Acess 2007 - cant create .accde

[SpaceMarine]

hello,

i am having a problem creating a .ACCDE file from an Access
2007 .ACCDB file.

its somewhat large application, about 80 megs. it was originally an
Access 2000 app that somebody else wrote for our user base, which ran
it as a .MDE. i have now converted it Access 2007 .accdb, and am to
use the "Make ACCDE" function off the Database Tools ribbon bar.

upon doing so it says i need to enable the content as a security
feature. no problem.

afterward tho, it reports:

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

....it has more info under "Show Help >>", which says the error is
usually associated w/ compiling large databases. dunno if that applies
to mine or not, since its the same app that Access 2000 was able to
convert to its .MDE format.


.....any thoughts of advice on things to try? im new to access, not
really the dev on this project, but tasked w/ the conversion.


thanks!
sm

 

[SpaceMarine]

i am having a problem creating a .ACCDE file from an Access
2007 .ACCDB file.

its somewhat large application, about 80 megs. it was originally an
Access 2000 app that somebody else wrote for our user base, which ran
it as a .MDE. i have now converted it Access 2007 .accdb, and am to
use the "Make ACCDE" function off the Database Tools ribbon bar.

upon doing so it says i need to enable the content as a security
feature. no problem.

afterward tho, it reports:

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

...it has more info under "Show Help >>", which says the error is
usually associated w/ compiling large databases. dunno if that applies
to mine or not, since its the same app that Access 2000 was able to
convert to its .MDE format.

....any thoughts of advice on things to try? im new to access, not
really the dev on this project, but tasked w/ the conversion.

ah...found a post on this. the error message is a typical MS red
herring -- what it really means to tell me, is that there is a problem
compiling one of the modules. evidently the only way you can locate
what & where is to open the VBA and attempt to Debug-->Compile there.

http://www.access-programmers.co.uk/forums/archive/index.php/t-123872.html


sm

 

[Tony Toews [MVP]]

ah...found a post on this. the error message is a typical MS red
herring -- what it really means to tell me, is that there is a problem
compiling one of the modules. evidently the only way you can locate
what & where is to open the VBA and attempt to Debug-->Compile there.

That's what it can mean yes. And it's quite standard to compile before making an
MDE. Actually I compile every few lines of code to catch any typos and such.

http://msmvps.com/blogs/access/arch...tton-every-few-lines-of-vba-code-i-enter.aspx

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/

 

[Tony Toews [MVP]]

...it has more info under "Show Help >>", which says the error is
usually associated w/ compiling large databases. dunno if that applies
to mine or not, since its the same app that Access 2000 was able to
convert to its .MDE format.

There actually is a limit in large MDBs in previous versions of Access. I would
expect that this limit has not been fixed in A2007 although I could be quite wrong.

You receive a "Microsoft Access Was Unable to Create an MDE Database" error message
in Access 2002
http://support.microsoft.com/kb/289686/

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/

 

[SpaceMarine]

That's what it can mean yes. And it's quite standard to compile before making an
MDE. Actually I compile every few lines of code to catch any typos and such.

nonetheless....i think the cause of this error is far more likely to
be a compile error (due to, say, typo) than for it to be a db size
issue. thus, the error description is a hopeless red herring that
will, more often than not, be completely inaccurate.


sm