H
Hubert Hoffman
I have a VB 6 app that uses ADO recordsets. I set up and
ODBC DSN to an Access database. The application connects
and is able to update the database/recordset UNTIL:
Another access2000 user opens the database, and opens a
form within the database. Once the form is opened, I am
unable to get the ADODB.Open function to work from VB. As
soon as the user closes access everything works again.
Doesn't matter machine, OS, user doesn't seem to matter,
once the form gets opened, the database is locked.
Has anyone experienced this, and is there a recommended
solution? How do I prevent the entire database from
getting locked when I open the form?
It was suggested, in another forum, that I might need to
develop my own recordset handler instead of using the
default access way of doing things, but no details were
given (looked complicated).
Thanks in advance,
Hubert Hoffman
ODBC DSN to an Access database. The application connects
and is able to update the database/recordset UNTIL:
Another access2000 user opens the database, and opens a
form within the database. Once the form is opened, I am
unable to get the ADODB.Open function to work from VB. As
soon as the user closes access everything works again.
Doesn't matter machine, OS, user doesn't seem to matter,
once the form gets opened, the database is locked.
Has anyone experienced this, and is there a recommended
solution? How do I prevent the entire database from
getting locked when I open the form?
It was suggested, in another forum, that I might need to
develop my own recordset handler instead of using the
default access way of doing things, but no details were
given (looked complicated).
Thanks in advance,
Hubert Hoffman