I have an issue where I have a split Access database that is accessed through both an Access front-end and a ASP.NET 2.0 web application. The database back-end resides on the web server and the Internet Guest account along with ASPNET account have full permission under the folder security. The ASP.NET 2.0 application accesses the Access database through an ODBC connection. On initial setup or after a server reboot everything works fine but the moment the web application is used (i.e. someone logs in) the Access front-end gives the user a 3073 error. The error states this query must be updatable which translates to the fact that a process of the web application has placed the db in exclusive "read-only" mode. If one trys to open the Access database directly on the web server the "This is in read-only" message appears.
My question how do I stop the web application (either IIS/ODBC or something else) from making the database read-only for all my other clients? I know this a configuration issue because I have this same setup working at a different site without this issue.
Windows Explorer lets you open cabinet (cab) files like any other folder.
In VBA you can easily handle normal files and folders, but opening and indeed creating cabinet files takes a lot more - and that's you'll find here.
With Microsoft Access, learn how to start a database in different ways and produce different start-up actions allowing you to use a single database to perform multiple tasks.
Specify a start-up form through options:
Specify an Autoexec macro: