Hi All, I tried the latest workaround for this error message (see below) related to access files stored on networks and used by multiple users, but it did not fix the problem. I continue to get the error message. Do I need to run the command on every PC that has used it? Are there any updates for solving this problem? It is a major issue for my company as we use Access in this manner all the time.
Although not a fix for your particular issue you may wish to consider upgrading your Access data to SQL Server or SQL Server Express, which is free. As a general rule we recommend any client with 3 or more users to upgrade, allowing you to leverage the best of SQL Server and Access together.
For more information on upgrading just your data to SQL Server, check out:
Please note: Just upgrading to SQL Server may not be enough, you may need to create views and stored procedures in order to get the performance you need, but it will be worth it in the end, since SQL Server is much more stable and has many other benefits over Access.