OT: 97 to 2003 MDE problems

T

TC

Hi folks

Sorry this is OT here, but I don't post to the other Access groups at
this time, so I need to ask your indulgence. I'm sure that someone here
will know.

I'm having desperate problems getting an access 2003 MDE from my access
97 MDB, for a national software launch in 10 days! I've done this
before, but it sure ain't working now.

The problem has various facets, but all of thm end with "VBA project is
corrupt". I've read all the info & kb articles on this, and I'm not
asking for a full rundown on all of the possible causes.

I have just one question:

What is current ageed best practice (if any) for converng an access 97
mdb to a later version (prepratory to creating an MDE from that later
version):

(1) DECOMPILE AND COMPACT the access 97 mdb (then convert to later
vesion, compile & save all, then make the hgher versin MDE)?

or:

(1) COMPILE & SAVE ALL & COMPACT the acess 97 mb (then convert to later
version, compile & save all, then make the higher vesion MDE)?

(1) seems the most logical to me, but some of the kb articles seem to
say (2).

I know about service pack issues & so on. I just need some input on the
single question above.

TIA
(the) TC
 
C

Chris Mills

IMHO,
Do everything you can to "clean" the 97 mdb of corruption before conversion,
and then everything you can to "clean" after conversion (as necessary). Does
it work as an mdb? (at least you can do a demo)

I have never seen posted a "best order". To me,
Decompile/Compile/Repair/Compact has always worked, in A97 and A2k.

Rick Brandt has posted more steps, such as
Repair/Decompile/Repair/Compile/Repair/etc... (as far as I could see, a repair
interposed at every step or something like that)

I always worry about that. You know what I mean.
Just IMHO
Chris
 
K

Keith

TC said:
Hi folks

Sorry this is OT here, but I don't post to the other Access groups at
this time, so I need to ask your indulgence. I'm sure that someone here
will know.

I'm having desperate problems getting an access 2003 MDE from my access
97 MDB, for a national software launch in 10 days! I've done this
before, but it sure ain't working now.
Hi TC, I hope I'm not teaching granny to suck eggs with this but there are
many issues with the conversion you're attempting. Have a look at Allen
Browne's site: http://allenbrowne.com/ser-48.html

Again, apologies if you already know about all this ...

Regards,
Keith.
 
J

Joan Wild

I agree with Chris. Clean up in 97 first. Are you able to make the mde in
97?

I would decompile, compile and save all, compact. Then see if you can make
a mde in 97.
If so then convert, compile, save, compact in 2003.
I wouldn't attempt a conversion until you can make the mde in 97.

If conversion isn't working, then try importing to a new mdb in 2003 (after
setting the references)
 
T

TC

Thanks for all replies, I appreciate the help. I have read all & will
consider where I go from now.

I can create the MDEs in 97, 2000, 2002 & 2003, it's just that the 2003
one fails in various mysterious ways, usually leading to a "VBA project
is corrupt" error.

I have, like, about 2 days to fix this! :-((

Cheers all,
TC
 
C

Chris Mills

One day now. We'd like to know too.

(Wildcards: reboot, try another PC or Access installation...Sp's...ultimately
importing everything...)
(never thought of Joan when I said wildcard)
Chris
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top