make mde error

  • Thread starter Thread starter rmanchu
  • Start date Start date
R

rmanchu

having worked on an Access 2003 mdb, i am now unable to make an MDE
from it, which i could before. the error says that i might be exceeding
the max number of TableIDs (2048)

under Tools>References i have
Visual Basic for Applications
Microsoft Office 11 Object Library
Microsoft Access 11 Object Library
Microsoft ActiveX Data Objects 2.8

in project i haveabout 20 forms (with code modules) and 6 modules

an (unknown) "acwdmain" and "acwdtool" which has numerous modules and
so on
is it possible to remove these two item? how?

help guys :(

riyaz
 
Try a restart. It is possible that you have the wizard code either loaded at
the time, or mixed with your own.

If that does not work, try recreating the database:

1. Under Tools | Options | Advanced, make sure you have "Default File
Format" set to "Access 2002/2003" since you want to be able to make an MDE
from A2003.

2. Create a new (blank) database.
Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html
Set the same references in the code window.

3. From the File menu, choose Import, and import the objects you do want:
tables, queries, forms, etc.

4. Open a code window, and check that the code compiles.

You should be able to create the MDE from this new file.
 
thanx

tried both. the acwd* objects r not there anymore (thankfully). but it
still does not compile saying that the TableIDs have possibly exceeded
2048

i repeat. havve about 20 forms and 6 modules. how can it exceed 2048?

my application uses Recordsets generated by VBA code to power all the
forms. but it compiled with that also before :( i've added 5 or so more
forms since the last MAKE MDE

riyaz
 
How many tables are in your database?

What do you get if you open the Immediate Window (Ctrl+G) in the new
database, and enter:
? DCount("*", "MSysObjects", "Type IN (1,4,6)")

Excuse the question, but does it say too many TableIDs or Databases?
 
number of tables in my MDE is 1 which is the switchboard. the
ado.recordsets that power my forms are retrieved from an mssql server


? DCount("*", "MSysObjects", "Type IN (1,4,6)")
7

Error Message:
This error is usually associated with compiling a large database into
an MDE file. Due to the method used to compile the database, a
considerable number of TableID references are created for each table.
The Microsoft Jet database engine version 4.0 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 Jet
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.
More information about this error message online.
 
Sorry: no idea.

Have never seen that message. Presumably it has to do with the possible
number of concurrent connections required for your recordsets for forms and
their subforms and combos and list boxes and domain aggregate functions and
so on.
 
having worked on an Access 2003 mdb, i am now unable to make an MDE
from it, which i could before. the error says that i might be exceeding
the max number of TableIDs (2048)

If you ever find a solution, please let the group know! I'm getting the same error
with Access 2003 on Win XP Pro.

Tom Lake
 
i found an problem that the MVPs have never seeeeeeeen. wow
now how am i going to distribute the front end ? :( :( :(

will do Tom. u 2 ok :)

tom, were u able to compile it before this happened? mine was. also
have u got API calls in ur modules? i've got three modules making
windows api calls.

perhaps, some of those api calls are not being compiled??? (wild guess)

riyaz
 
I don't know if my information is 100% relevant to your problem, but I used
to encounter failures to create MDE files and discovered that my problems
related to forms that I copied and pasted to the same database, then changing
the form names to meet my needs.

I learned the hard way that any code (event procedures) I had transferred
over when copying the form created a conflict (for MDE creation).
------------------------
My solution:
My workaround was to create a brand new form and perform copy and paste jobs
on all objects in my form. This, of course, is "labor-intensive" when you
have several pages to re-build. But by having a fresh form when completed
that replicates another in the same database, I was able to create the MDE
file.
------------------------
So, even if your event procedure coding is accurate and valid, the problem I
encountered was in duplicaing a particular form by copying the form and
renaming it. I found that I cannot simply export a data entry form, with
heavy event procedure coding, from one database to another and expect the
ability to create an MDE file. The database may work all right as an MDB
file, but I can never get such a database with an imported data entry form
(with coding) into MDE format.

Tank
-------------------------------------------------------------------
 
Back
Top