We have a VB6 application that accesses a MS Access database with both DAO and ADO.
When running on Windows 7 (VB6 app is runtime executable) with different user accounts we have encountered a very strange occurrence. When running the application under an administrator account we key some entries into the database. When running the application on the same machine under a standard user account, the new entries made by the administrator account cannot be seen. Nor can entries made by the user account be seen by the administrator account. This is after the application has been closed between each session, so is not a matter of recordsets not being refreshed or anything like that.
The workaround we have found is to set the application to "Run as administrator". However, we are finding clients that do not want to set their users up as administrators, nor require them as standard users to key an administrator password to start the application up. We have also found a solution for setting the administrator password in the credential manager so can get around this.
However, my question is, why does there appear to be 2 separate versions of the database from the 2 accounts? Why are transactions made by one user not visible to the other user even after exiting? The database seems to be stored in two different virtual storage spaces. Is there some other solution to this issue besides requiring the application to "Run as administrator"?
Thanks for any help.
When running on Windows 7 (VB6 app is runtime executable) with different user accounts we have encountered a very strange occurrence. When running the application under an administrator account we key some entries into the database. When running the application on the same machine under a standard user account, the new entries made by the administrator account cannot be seen. Nor can entries made by the user account be seen by the administrator account. This is after the application has been closed between each session, so is not a matter of recordsets not being refreshed or anything like that.
The workaround we have found is to set the application to "Run as administrator". However, we are finding clients that do not want to set their users up as administrators, nor require them as standard users to key an administrator password to start the application up. We have also found a solution for setting the administrator password in the credential manager so can get around this.
However, my question is, why does there appear to be 2 separate versions of the database from the 2 accounts? Why are transactions made by one user not visible to the other user even after exiting? The database seems to be stored in two different virtual storage spaces. Is there some other solution to this issue besides requiring the application to "Run as administrator"?
Thanks for any help.