Problem saving Database as .accde format

[Thorson]

I have been making changes to the front end of my database and then saving to
an .accde format for a while now, using the auto FE updater to update the
database the users see. However this time when I tried to save it as a
..accde copy it would not work an error came up stating:

"Microsoft Office Access was unable to create the .accde, ,mde, or .ade file."

Under "Show Help" it says:
This error is usually associated with compiling a large database into an MDE
file. Because of the method used to compile the database, a considerable
number of TableID references are created for each table. The Access database
engine can only create a maximum of 2048 open TableIDs at one time.
Exporting a database as an MDE potentially can exceed this limit if the
database has a large number of objects (table, macro, form, report, etc).
There is no accurate method to estimate the number of TableIDs the Access
database engine uses during the process of compiling a database as an MDE.
However, each VBA module and each form uses one TableID, as a result, if the
database has 500 forms, and each form's HasModule property is set to Yes, as
many as 1,000 TableIDs are used.

I don't know what this means or what to do. I am using Access 2007. If
anyone can help I would appreciate it! Thanks

 

[Douglas J. Steele]

Make sure your accdb compiles.

 

[Dirk Goldgar]

I have been making changes to the front end of my database and then saving
to
an .accde format for a while now, using the auto FE updater to update the
database the users see. However this time when I tried to save it as a
.accde copy it would not work an error came up stating:

"Microsoft Office Access was unable to create the .accde, ,mde, or .ade
file."

Under "Show Help" it says:
This error is usually associated with compiling a large database into an
MDE
file. Because of the method used to compile the database, a considerable
number of TableID references are created for each table. The Access
database
engine can only create a maximum of 2048 open TableIDs at one time.
Exporting a database as an MDE potentially can exceed this limit if the
database has a large number of objects (table, macro, form, report, etc).
There is no accurate method to estimate the number of TableIDs the Access
database engine uses during the process of compiling a database as an MDE.
However, each VBA module and each form uses one TableID, as a result, if
the
database has 500 forms, and each form's HasModule property is set to Yes,
as
many as 1,000 TableIDs are used.

I don't know what this means or what to do. I am using Access 2007. If
anyone can help I would appreciate it! Thanks

Despite the message, the most common cause of this failure is a compile
error in the original database. Did you first explicitly compile the ACCDB
using the VB editor's Debug -> Compile menu item?

 

[Thorson]

I don't think I did that, because I'm not even sure how...

 

[Dirk Goldgar]

I don't think I did that, because I'm not even sure how...

Does your database contain any VBA code? If you only ever used macros, it
wouldn't contain any VBA, and compiling wouldn't be an issue.

To compile it, press Alt+F11 to bring up the VB Editor window. In that
window, click menu item Debug -> Compile. If there are any errors in the
VBA code, it will show them to you. Keep fixing errors and comnpiling until
your project compiles without errors. Then try making your ACCDE.

 

[Thorson]

Thank you! That was the problem. I guess I had always tested and fixed my
errors before trying to save in the past.

Thanks!

 

[David W. Fenton]

I guess I had always tested and fixed my
errors before trying to save in the past.

I don't understand any Access programmer who doesn't compile
literally hundreds of times a day during working hours. I compile
after every two or three lines of code.

 

[Tony Toews [MVP]]

I don't understand any Access programmer who doesn't compile
literally hundreds of times a day during working hours. I compile
after every two or three lines of code.

Agreed. Indeed I created a button on the toolbar to compile.

Tony

 

[David W. Fenton]

Agreed. Indeed I created a button on the toolbar to compile.

This is likely because you were trying to recreate the Access 97
environment, where the Compile button was on the default module
toolbar. Also, the Call Stack button was there, and I always add it
to the code window toolbar.

 

[John W. Vinson]

I do so routinely as well (it's easy, just customize the toolbar and drag it
from the Debug menu list).

This is likely because you were trying to recreate the Access 97
environment, where the Compile button was on the default module
toolbar. Also, the Call Stack button was there, and I always add it
to the code window toolbar.

Ummm... showing my ignorance here... what does "Call Stack" do?

 

[David W. Fenton]

Ummm... showing my ignorance here... what does "Call Stack" do?

Heavens! In break mode, it shows you the order of calling
subroutines and allows you to navigate them so you can see the
calling context of the code with the break. I don't see how anyone
can debug code without using it!

 

[o;;]

I don't understand any Access programmer who doesn't compile
literally hundreds of times a day during working hours. I compile
after every two or three lines of code.