mde creation: Produce Code compilation error if required

[Guest]

If I attempt to convert my mdb file to an mde file and the conversion fails
because of a code error, I only get the error that suggests I might have too
many table IDs. This error is misleading because the root cause of failure is
erroneous code. I then go to the VB editor and compile to see where my error
is. I fix the error and retry with success. Problem is I had to search the
internet for the solution, not your help files.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-867f-a6dbf727f474&dg=microsoft.public.access

 

[Guest]

Hi Chibby,

I just get an error message that reads "Microsoft Access was unable to
create an MDE database", if I purposely leave code that will not compile. The
error I see does not include any mention of too many table ID's. However, it
is very possible that you had two problems going: Too many table ID's and
code that would not compile. Only the first problem was flagged with the
error message that you read. A compact and repair operation could very well
have fixed that problem. Here is a link that I think you may find helpful:

Cannot make .MDE
http://www.access.qbuilt.com/html/conversion.html#CannotMakeMDE


Perhaps get in the habit of compiling your code and compacting your database
on a frequent basis. Also, remove the Compile on Demand option that is set by
default. This option can allow some code to work as designed, while other
code in the same VBA project will not compile. If you clear the checkbox, and
you have a compile error, none of your code will work until you fix the
compile error. See the topic:

"Avoid Compile on Demand"
http://www.access.qbuilt.com/html/VBEOptions (scroll down a bit)


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Granny Spitz via AccessMonster.com]

I just get an error message that reads "Microsoft Access was unable to
create an MDE database", if I purposely leave code that will not compile. The
error I see does not include any mention of too many table ID's.

That's because you aren't using Access 2003. The Access 2003 help tells you
when "Microsoft Access was unable to create an MDE database," it's usually
due to too many TableIDs. Very, very misleading. The failure is rarely due
to too many TableIDs. As an MVP, maybe you could tell Microsoft what the
usual causes are so they can ammend this help message in the next version?

 

[Guest]

Granny,

How right you are! I've been using Access 2002 for the last couple of days,
because I've been busy using Total Access Analyzer, version 10.5 (Access 2002
version) on several databases. While I have Access 2003, I simply wasn't
using it when I ran that quickie test. I wasn't aware of the change in the
text of the error message between versions.

As an MVP, maybe you could tell Microsoft

I'm sure they're aware of Gunny's list!


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________