MDE encrypter 2048 Table IDs limitation

F

FreeWheel

Hi,

My application holds many tables and very many queries, reports and forms...
JET will not compile because of too many Table ID references (over 2048).

How do I get around this ?

Tks
 
T

Tony Toews [MVP]

FreeWheel said:
My application holds many tables and very many queries, reports and forms...
JET will not compile because of too many Table ID references (over 2048).
Click to expand...

The only way around this is to reduce the number of objects.
Possibly split up your MDB into two by function.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
T

Tom van Stiphout

On Sat, 18 Oct 2008 11:14:01 -0700, FreeWheel

Export everything to a fresh database and try again.
If that does not help, you may have exceeded the Access design
specifications, and you should be looking for a different DBMS.

-Tom.
Microsoft Access MVP
 
G

Guest

Import everything into a new database (to remove
any dead object count).

If that doesn't work, break the database into a couple
of library databases, and reference them from a shell
database.

(david)
 
C

Chris O'C via AccessMonster.com

Are you sure that's really the problem? The help gives that excuse when the
mdb can't be converted into an mde for *any* reason. That's when the code
isn't compiled, the db format isn't in the current version of Access, missing
activex controls, missing libraries, reference libraries in mdb format, etc.

Rule out the common mistakes which prevent conversion to mdes before you
assume there aren't enough table ids. You'll probably save yourself a lot of
unnecessary work.

Chris
Microsoft MVP
 
C

Chris O'C via AccessMonster.com

After reading your other posts, I see you have a vba password set. Remove
the vba password before trying to convert to mde, because that prevents
conversion.

Chris
Microsoft MVP
 
C

Chris O'C via AccessMonster.com

To prevent this from happening again, add these 2 words to the top of every
code module:

Option Explicit

In the menu Tools > Options, click on the "Require Variable Declaration"
checkbox so option explicit is added to all new code modules.

Chris
Microsoft MVP
 
T

Tony Toews [MVP]

Chris O'C via AccessMonster.com said:
Are you sure that's really the problem? The help gives that excuse when the
mdb can't be converted into an mde for *any* reason. That's when the code
isn't compiled, the db format isn't in the current version of Access, missing
activex controls, missing libraries, reference libraries in mdb format, etc.

Rule out the common mistakes which prevent conversion to mdes before you
assume there aren't enough table ids. You'll probably save yourself a lot of
unnecessary work.
Click to expand...

Geez, I keep forgetting that can be the cause of this message.

Thanks, Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
S

Sky

Chris O'C via AccessMonster.com said:
After reading your other posts, I see you have a vba password set. Remove
the vba password before trying to convert to mde, because that prevents
conversion.

Chris
Microsoft MVP
Click to expand...

Hm, in Access 2003, I am able to compile a database to an mde even though
there is a VBA password.

- Steve
 
C

Chris O'C via AccessMonster.com

In some Access versions when the vba project is locked for viewing, if you
don't give the vba password first or clear the vba password, the mdb won't
convert to an mde.

Chris
Microsoft MVP
 
Top