Access apd will not allow forms to be deleted or renamed

Posted on 2015-02-18
Last Modified: 2016-02-11
I've developed an Access .adp application (Access 2010/SQL 2008R2) which works fine - but if I try to rename a form or delete a form the sub menu that opens when you right click on the form has the Delete and Rename option greyed out.

I created a blank database and imported all the forms/reports/macros/modules successfully from the Access.adp front end database and connected the front end database to the back end SQL database but sill no joy with being able to rename/delete forms.

I have opened all tables/ forms - just to make sure there was no problems - everything opened as expected and I even recompiled the front end database - still no joy.

I have several other Access.adp databases running in the same PC/Server and all allow me to rename/delete forms/reports etc.

Is there some system setting that I should set on/off?

Many thank for you assistance
Question by:Adlerm
  • 2
  • 2
LVL 84

Assisted Solution

by:Scott McDaniel (Microsoft Access MVP - EE MVE )
Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 167 total points
ID: 40618838
Try to Decompile the application. To do that, create a Shortcut with this as the Target:

"full path to msaccess.exe" "full path to your db" /decompile

Do that, then Compact the database. Next, open the VBA Editor and Click Debug-Compile. Fix any errors, and continue doing that until the menu item is disabled. Now compact again.
LVL 24

Assisted Solution

Bitsqueezer earned 333 total points
ID: 40622074

I made a module which exports any object in an ADP into a new ADP including the Access properties and VBA references. It uses Application.LoadFromText and Application.SaveAsText to export and import which makes sure that the result are decompiled text objects so any "binary trash" is removed in the new database file. I use that from time to time to refresh my ADPs during development and helped me often.

The module can be found here:



Author Comment

ID: 40622517
Hi Scott / Christian

Scott I tried you suggestion but it did not fix my problem.
Christian I' still to test you approach.

As a background note I should have said the frontend Access.adp database that I'm having trouble with was originally developed under Access 2007 and transported across to Access 2010.  The other Access.adp applications I referred to were developed only under Access 2010.

To bring you up to date I think I have identified the cause but I don't know why it is causing it.

I created a new frontend Access.adp (2010) database linked to the backend SQL Server database and then imported all the object groups (forms/reports/macro/modules - in that order) from the old frontend database.

I checked the form's submenu after importing each object group, closed the application and then reopened it again checking the forms submenu. Rename/Delete options on the form's submenu were active on all occasions, however, after importing the Modules object group, closing the application and the reopening it I started to get compile error messages.

I then started to check various references (e.g. Visual Basic For Applications, Microsoft Access 14.0 Object Library etc.). Again everything was OK - with respect to the forms' submenu Rename/Delete options - until I checked the Microsoft DAO 3.6 Object Library.

After checking the Microsoft DAO 3.6 Object Library reference I recompiled the program (this got rid of the compile error I was encountering ) checked the forms' submenu (Rename/Delete options still active) and closed the application.

Unfortunately on reopening the application - at this stage - The form's submenu Rename/Delete options were no longer active (greyed out).

I carried out a number of other tests - to verify if the Microsoft DAO 3.6 Object Library reference was the culprit - by removing it from the reference list and then adding it back into the reference list. Each time the reference was removed from the reference list the form's submenu Rename/Delete options were active after reopening the application. Conversely, the form's submenu Rename/Delete options were not active if the Microsoft DAO 3.6 Object Library reference was included in the reference list.

Hope this may shed some light on the problem.

Many thank for your assistance

Michael Adler
LVL 84
ID: 40622832
DAO 3.6 generally is not used with 2007 and above. Instead, you use the "Office xx Access Database Engine Object Library", as you've indicated.
LVL 24

Accepted Solution

Bitsqueezer earned 333 total points
ID: 40623079
Hi Michael,

as Scott said, the DAO library was exchanged beginning with A2007, because the database engine was exchanged from JET to ACE. But if you do not explicitly need DAO for any reason in your frontend you can completely remove it as an ADP normally don't need DAO, only ADO (which also should be version 6.x depending on the target Windows version you want to use - beginning with Windows Vista it should be 6.x, in case of Windows XP it should be version 2.8, and the frontend should only compiled on a Windows XP machine then as the 2.8 from >=Vista is not compatible with the 2.8 from XP).

As you can also use ADO to open an ACCDB/MDB (if you want to do that in your ADP frontend) you should rewrite DAO code to ADO code in your frontend and remove the DAO reference completely from your frontend.



Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Excel Conditional Statements 11 39
"Fit to Drawing" different Layers 7 25
macro modification Column C 14 31
Rename a column in the output 3 14
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Some code to ensure data integrity when using macros within Excel. Also included code that helps secure your data within an Excel workbook.
With Microsoft Access, learn how to specify relationships between tables and set various options on the relationship. Add the tables: Create the relationship: Decide if you’re going to set referential integrity: Decide if you want cascade upda…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question