Can't make an MDE in Access 2003

[pw]

Hi,

I converted (actually, imported) my Access 97 application into Access
2003. I selected "Create MDE" and it prompts me for the mde file to
create. However, what A2003 really does is create a MDB called
db1.mdb, then locks up!!

It looks like that menu pick is actually compacting the database, NOT
creating an MDE!

How do I create an MDE in Access 2003?

-pw

[CDB]

Paul, I suggest you go back and convert a copy of the A97 db. That will fix
some problems. But not all.

Then, go to the VB editor, and try to compile all. If it fails, find the
cause of the first failure. Repeat until compiled.

Then compact the db.

Then try the MDE part.

The process includes an automatic, unavoidable compact, which could fail if
there are problems. That is what you are seeing. The stripping out of code
occurs after Access has satisfied itself that it is reasonably safe to do
so.

Clive
"pw" <pa************@spamcop.net> wrote in message
news:e3**************************@posting.google.c om...

Hi,

I converted (actually, imported) my Access 97 application into Access
2003. I selected "Create MDE" and it prompts me for the mde file to
create. However, what A2003 really does is create a MDB called
db1.mdb, then locks up!!

It looks like that menu pick is actually compacting the database, NOT
creating an MDE!

How do I create an MDE in Access 2003?

-pw

[David W. Fenton]

"CDB" <al***@delete.wave.co.nz> wrote in
news:c4**********@news.wave.co.nz:

Paul, I suggest you go back and convert a copy of the A97 db. That
will fix some problems. But not all.

I'd say that you should try creating an MDE in A97 before
converting. It will probably fail.

Then decompile the A97 MDB and recompile it to find out what's wrong
with it, fix that, then try to create the A97 MDE. If it succeeds,
then conversion to A2K3 and saving as MDE should work without a
hitch.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[CDB]

Ah, yes! An assumption on my part.

But my experience in converting from A97 to A2K, AXP and A03 is that there
can be problems during conversion even so, and that there can be slightly
different behaviours producing undesired results.

Clive
"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:Xn**********************************@24.168.1 28.74...

"CDB" <al***@delete.wave.co.nz> wrote in
news:c4**********@news.wave.co.nz:

Paul, I suggest you go back and convert a copy of the A97 db. That
will fix some problems. But not all.

I'd say that you should try creating an MDE in A97 before
converting. It will probably fail.

Then decompile the A97 MDB and recompile it to find out what's wrong
with it, fix that, then try to create the A97 MDE. If it succeeds,
then conversion to A2K3 and saving as MDE should work without a
hitch.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[David W. Fenton]

"CDB" <al***@delete.wave.co.nz> wrote in
news:c4**********@news.wave.co.nz:

But my experience in converting from A97 to A2K, AXP and A03 is
that there can be problems during conversion even so, and that
there can be slightly different behaviours producing undesired
results.

But the first thing to test is whether or not the source file is
good in the first place. I also think that it's really a good idea
to never convert to A2K+ from A97 unless the A97 file is in a
pristine state (decompiled/recompiled/compacted), because certain
kinds of code and form corruption can survive the conversion (just
as they can survive and import).

Last, it's my opinion that most of the problems encountered in
converted databases were problems *before* the conversion, and
fixing them in the source version is likely to be a better fix than
fixing them once converted.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc