Cannot make MDE file

[Adam]

Hi,

I'm trying to make an MDE file but error message
says "Microsoft Access was unable to create an MDE
database"

Password to database is removed.
Password to VBEditor is removed.
There are no replications.
db is one whole db, not split into f & b ends.

Can anyone provide some helpful suggestions?

Thanks

Adam
I just don't know what the hell I'd do without these
Newsgroups.

 

[Tom Wickerath]

Hi Adam,

There are two main reasons why people cannot convert a .MDB file to a .MDE file:

1.) The file format does not match the version of Access. In this case, the option to create a
..MDE file will be unavailable (ie. "grayed out"). Use Tools > Database Utilities > Convert
Database and select the current version that matches your version of Access.

2.) You have VBA code that is not compiling properly. Part of the process of creating a .MDE
file involves removing all of the canonical text (VBA code that you can read). In order to do
this, the project must compile without any errors. Open the VBA editor (ALT F11) and then
select Debug > Compile DatabaseName. Correct any compile errors before attempting to convert
your database to a .MDE file.

Tom
________________________________________


Hi,

I'm trying to make an MDE file but error message
says "Microsoft Access was unable to create an MDE
database"

Password to database is removed.
Password to VBEditor is removed.
There are no replications.
db is one whole db, not split into f & b ends.

Can anyone provide some helpful suggestions?

Thanks

Adam
I just don't know what the hell I'd do without these
Newsgroups.

 

[Adam]

Hi Tom,

1.) The file format does not match the version of

Access. In this case, the option to create a

..MDE file will be unavailable (ie. "grayed out"). Use

Tools > Database Utilities > Convert

Database and select the current version that matches your

version of Access.

Using Access 2000. This didn't work as it tried to make a
prior version which in turn needs to be converted back to
2000 in order to work with A2K

2.) You have VBA code that is not compiling properly.

Part of the process of creating a .MDE

file involves removing all of the canonical text (VBA

code that you can read). In order to do

this, the project must compile without any errors. Open

the VBA editor (ALT F11) and then

select Debug > Compile DatabaseName. Correct any compile

errors before attempting to convert

your database to a .MDE file.

Tom

I couldn't believe it. There were bugs everywhere...about
20. Why weren't these bugs picked up beforehand in routine
compiling?

MDE now successfully created.

Many thanks for that.

Adam

 

[Arvin Meyer]

Adam,

If there is any possibility of 2 people sharing an Access file, it is
extremely important that you split your database to avoid corruption. The
MDE need only be placed on the front-end as it doesn't do anything on the
back-end (data) anyway.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Tom Wickerath]

Hi Adam,

Given that you are using Access 2000, and the only other choice was to convert to Access 97, then
your database was already in the Access 2000 format. In fact, I suspected this, since your
original problem statement did not indicate that the option to create a .MDE file was
unavailable. I listed the first issue as part of a generic solution that could possibly help
others as well--or perhaps help you when you eventually upgrade to a later version of Access.

Why weren't these bugs picked up beforehand in routine compiling?

Were you routinely compiling your database beforehand? Compiling the code is not the same as
running the compact and repair operation. If you were compiling your code routinely before, then
I really don't have an immediate answer without knowing more about the approx. 20 errors that you
found.

Tom
__________________________________________


Hi Tom,

1.) The file format does not match the version of Access. In this case, the option to create a

..MDE file will be unavailable (ie. "grayed out"). Use Tools > Database Utilities > Convert
Database and select the current version that matches your version of Access.

Using Access 2000. This didn't work as it tried to make a prior version which in turn needs to be
converted back to
2000 in order to work with A2K

I couldn't believe it. There were bugs everywhere...about 20. Why weren't these bugs picked up
beforehand in routine
compiling?

MDE now successfully created.

Many thanks for that.

Adam
________________________________________



Hi Adam,

There are two main reasons why people cannot convert a .MDB file to a .MDE file:

1.) The file format does not match the version of Access. In this case, the option to create a
..MDE file will be unavailable (ie. "grayed out"). Use Tools > Database Utilities > Convert
Database and select the current version that matches your version of Access.

2.) You have VBA code that is not compiling properly. Part of the process of creating a .MDE
file involves removing all of the canonical text (VBA code that you can read). In order to do
this, the project must compile without any errors. Open the VBA editor (ALT F11) and then
select Debug > Compile DatabaseName. Correct any compile errors before attempting to convert
your database to a .MDE file.

Tom
________________________________________

message
Hi,

I'm trying to make an MDE file but error message says "Microsoft Access was unable to create an
MDE database"

Password to database is removed.
Password to VBEditor is removed.
There are no replications.
db is one whole db, not split into f & b ends.

Can anyone provide some helpful suggestions?

Thanks

Adam
I just don't know what the hell I'd do without these Newsgroups.

 

[Adam]

Only one user is using it. It is a db that is constantly
being updated with new features and has been a great
experiment so far in my development.

Haven't been concerned about corruption because the db is
backed up daily, so, if major corruption (ie more than
just a corrupt table) were to occur then the user must
recall the most recent backup.

Are you suggestion that where more users are using the db
that corruption could ensue because of more users?

aj

 

[Adam]

Hi Tom.

I apologise for not being more specific about the problem
domain. I'll be more careful next time.

-----Original Message-----
Hi Adam,

Given that you are using Access 2000, and the only other

choice was to convert to Access 97, then

your database was already in the Access 2000 format. In

fact, I suspected this, since your

original problem statement did not indicate that the

option to create a .MDE file was

unavailable. I listed the first issue as part of a

generic solution that could possibly help

others as well--or perhaps help you when you eventually

upgrade to a later version of Access.

compiling?
Were you routinely compiling your database beforehand?

Compiling the code is not the same as

running the compact and repair operation. If you were

compiling your code routinely before, then

I really don't have an immediate answer without knowing

more about the approx. 20 errors that you

found.

I thought Access compiles automatically whenever code is
being run. In other words, write the code, then run it. If
there are problems, Access complains and we get "error
messages". The 20 bugs I'm referring to are bugs that have
been part of a db that has being working happily for the
last eight months or so without complaints.

There must be 'two' compilers!

Regards

Adam

 

[Tony Toews]

Are you suggestion that where more users are using the db
that corruption could ensue because of more users?

If users are sharing the MDB when it should be split into a FE/BE that
can be a cause of corruptions. Or sharing the FE on the server can
be enough to cause corruptions.

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