Conversion issue

[TJ Dowling]

I have taken over the development of an application that the previous
developer used Access 2003 to develop an application for a user with Access
2000. Once he had written enough code to test, he would convert the mdb file
to version 2000 for testing on the client's machines.

It worked fine for a while. Now when I try to run certain reports in Access
2000, the Access window shuts down whenever it hits the report object. I can
get to the reports design view in Access 2003 but not in 2000. If I try to
design, preview or open the report object in 2000 the Access window shuts
down but leaves the ldb file.

I know it sounds kind of weird but its stopping me cold in my tracks.

Any ideas?
I want to do all of the development in version 2000 but can't get the report
objects to cooperate.

I have some reports that I'm trying to develop bu

 

[Allen Browne]

This sounds like the kind of corruption that a decompile would fix.

Try this sequence (in order):

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

7. Still in the code window, choose Options on the Tools menu. On the
General tab, make sure Error Trapping is set to:
Break on Unhandled Errors
and the Compile on Demand is unchecked.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
the code syntax is compilable, and the VBA options are set to show errors
and avoid this kind of corruption.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

 

[TJ Dowling]

Allen,

Thanks for the tip. It worked!

TJ Dowling