The security wizard cannot be run on a database when you are both logged on as the Admin user and the wizard has previously run on the database. To fix this problem, you may log on as another member of the Admins group or import all objects to a new database.
The row you inserted in the grid exceeds the limit of 255 rows (fields) for a table or 1,000 rows (actions) for a macro.@1@1 ...
The rows you modified could not be saved to the server due to validation errors. This is usually caused by invalid default ...
The section width is greater than the page width, and there are no items in the additional space, so some pages may be blank.@For ...
The Security Wizard cannot be run on a database that has open objects that have not been saved. Save all open database objects ...
The security wizard cannot be run on a database when you are both logged on as the Admin user and the wizard has previously ...
The Security Wizard cannot be run on a project when the Visual Basic Environment (VBE) project password has been set. You ...
The Security Wizard creates an unsecured backup copy of the current Microsoft Access database and takes steps to help secure ...
The Security Wizard has encoded your database. To re-open your database, you must use the new workgroup file you have created, ...
The Security Wizard report that is created upon completion of the wizard requires you to have a default printer set up. The ...