error message appears when saving design changes to a database in MS Access

[Ander K]

Error message comes after open, when attempting to create a database object in Design view, or to save design changes to a database object that may occur this error. An exclusive lock on the database is required for some of the Access object types, because other users might try to use these objects. This error indicates that Access has received an exclusive lock on the database. If the name of a table or field definitions have changed, while someone has opened the table, this will cause a fatal error for the other users. Therefore, you need to update a object have exclusive access to the database. If you remove the exclusive lock, other users can use the database again. It is recommended that you use to program source code control using Microsoft Visual SourceSafe Add-ins to implement Microsoft Access. Alternatively, you can also distribute local working copies of the database to each developer. Why does this error message occurs? It does not attempt to open forms in design mode!! Office 2007 came with no error message, it appears only since after the installation of Office 2010. After 3 - 6 times clicking it, the error message disappears and the form opens. If the form is closed and re-open no longer appears the error message. User PC's have their own software: Windows 7 with 32-bit and Office 2010 (Access 2010). Database file is stored on hard disk of the server (Windows Server 2003) and is designed for users on the corporate network without restrictions released. Please help me to resolve this issue.

[Mrigankasekhar]

This predicament occurs when you try to open a form, report, macro, module, or command bar in Design view. This issue also takes place when you attempt to save design changes to one of these object types or a new page link while additional users presently have the same database open. To save design changes to these object types, Access must be able to achieve an exclusive lock on the database. Also another thing is that, when numerous developers are designing an Access application concurrently, you can implement source code control by using the Microsoft Visual SourceSafe Add-In for Microsoft Access. Otherwise, you can allocate local working copies of the database to each developer.

[KennedII]

You have an Access application that consists of only a single file, so a MDB or MDE. This causes many problems for example the file is often broken, or it swells up excessively or you need for every little change the application block. Access applications should, in principle of two (or more) existing files. Especially in multi-user operating an allocation in the front end (FE) and backend (BE) is called for urgently. Under Backend is meant by an Access MDB, which contains only the tables. The front end contains all other database objects (forms, reports, queries, macros, modules) and the attached tables from the backend. For applications in the network should get their own each workstation, as local FE, while the BE is shared on the server. The reasons for these actions:

• Without division into FE and BE occurs in multi-user access often damage the file. FE-BE-sharing these corruptions are much rarer. If the FE but once damaged, it can easily be replaced without data loss.
• By local FEs, there is less network traffic because only the data must go over the net.
• Design changes to a front-end copy at any time.

For the division into FE and BE provides access a wizard (Tools / Database Utilities / Database Splitter Wizard). The distribution is also relatively easy without a wizard, by importing into a new MDB tables, it deletes the FE and then re-integrates.

[Christina 80]

You have problems with the setup of the Office Developer Edition. Either already when creating the setup or install the generated runtime packages. he runtime creation and installation with the Setup Wizard or the A97 Package and Deployment Wizard from A00 is unfortunately legendary unreliable and prone to error. To pass on a run, necessarily a license to the appropriate Office Developer version is required. But you must not use the included Setup creators. There are some alternatives also. Inno Setup is a popular freeware program for guides, scripts (for A97), newsgroups, etc. are freely available. This script can avoid the problems of the Assistant. Inno Setup addition, there are many other freeware and shareware installers. So just need to start a corresponding Internet search. For these two installer offers the company in relatively expensive, but professional and reliable scripts for all current versions of Access, which in turn avoid the mistakes and problems of the Office Installation Wizard.