funky decompile behavior

[ragtopcaddy via AccessMonster.com]

I've decompiled mdbs before and then gone to debug/compile in the toolbar and
recompiled. This mdb is not giving me the opportunity to recompile in the
debug menu after a decompile. I have tried both:

"Path to MSACCESS.EXE" "Path to mdb" /decompile and
"Path to MSACCESS.EXE" /decompile "Path to mdb"

In both cases the decompile apparently didn't work.

I am using Access03 SP2, but I think the original file was a 2002 file. Could
that be the culprit?

Thanks,

--
Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

Message posted via AccessMonster.com

 

[Tony Toews [MVP]]

I've decompiled mdbs before and then gone to debug/compile in the toolbar and
recompiled. This mdb is not giving me the opportunity to recompile in the
debug menu after a decompile. I have tried both:

"Path to MSACCESS.EXE" "Path to mdb" /decompile and
"Path to MSACCESS.EXE" /decompile "Path to mdb"

In both cases the decompile apparently didn't work.

Now that doesn't make a lot of sense.

When you start the above command hold down the shift key so your
startup code doesn't execute. Then compact & repair the MDB. You
should see a very significant decrease in MDB size. The compile and
the MDB size should significantly get bigger.

If that still doesn't work then try importing all objects into a new
MDB.

I am using Access03 SP2, but I think the original file was a 2002 file. Could
that be the culprit?

Doubtful.

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/

 

[ragtopcaddy via AccessMonster.com]

Thanks for the feedback, Tony,

Before I went to all the trouble of importing all the objects to a new db, I
wanted to be more confident that it was, in fact, corrupt. I inherited it.

Thanks again,

Bill

I've decompiled mdbs before and then gone to debug/compile in the toolbar and
recompiled. This mdb is not giving me the opportunity to recompile in the

[quoted text clipped - 4 lines]

In both cases the decompile apparently didn't work.

Now that doesn't make a lot of sense.

When you start the above command hold down the shift key so your
startup code doesn't execute. Then compact & repair the MDB. You
should see a very significant decrease in MDB size. The compile and
the MDB size should significantly get bigger.

If that still doesn't work then try importing all objects into a new
MDB.

I am using Access03 SP2, but I think the original file was a 2002 file. Could
that be the culprit?

Doubtful.

Tony

--
Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

Message posted via AccessMonster.com