I have written an application that makes significant use of ADO connections to an Access database. This is the first application I have written using VB (v6 SP4). Everything works terrifically when single user is logged in, even over the network connections. My problem is when more than one user attempts to navigate around the same ADO intensive areas of the application. I get "Database placed in a state by unknown user that prohibits open or access to database" (I can\'t remember the exact wording). It can\'t be a Locking problem as all ADO connections are specified as Readonly, ClientSide and Static.
\r\nIs this a problem with Access running out of resources ? Has anyone got any ideas ?
\r\nAll users login to the database with the same \'Admin\' name with no password. I am using UDL files to specify the connectinon parameters.