Corrupted report converting from Access 2002 to Access 97

[Alain Vaillancourt]

I converted an Access 2002 database to Access 97 and when I try to open a
report in the resulting database, I get the message "It contains data that
Microsoft Access doesn't recognize". I repaired the original database and I
also tried to import the report in a new database before converting it but
it doesn't change anything.

Thanks for any suggestions...

 

[Allen Browne]

Using A2002, open the report in design view.
Is there anything in its module? Anything specific to A2002, such as code
that references its OpenArgs or uses a custom enumeration?

If there is no code, check the report's HasModule property. Set it to No if
it's not already set that way. (ONLY do that if there is no needed code in
the module.) Then compact the database.

Name AutoCorrect can cause the kind of corruption you describe. Details:
http://allenbrowne.com/bug-03.html

Another option is to export the report to a text file, using the
undocumented SaveAsText. Open the Immediate Window (Ctrl+G) and enter:
SaveAsText acReport, "Report1", "C:\report1.txt"
Then create a new (blank) database using A2002, and get Access to recreate
the report from the text file with:
LoadFromText acReport, "Report1", "C:\report1.txt"
Then try converting this mdb to A97.
Then import the report into the A97 datbabase that lacks this report.

 

[Alain Vaillancourt]

Thanks for your answer. I don't use anything specific to A2002, in fact I
use exactly the same code in another report that don't cause any problem. So
what I done is to erase the code (setting HasModule to false) in the
problematic report and after the conversion, I copied and pasted the code
from the good report in the problematic one. All is working this way but the
problem is still there, everytime I convert my db I need to remove the code
so if someone has a permanent solution it would be appreciated.

 

[Peter Gillett]

Thanks for your answer. I don't use anything specific to A2002, in fact I
use exactly the same code in another report that don't cause any problem. So
what I done is to erase the code (setting HasModule to false) in the
problematic report and after the conversion, I copied and pasted the code
from the good report in the problematic one. All is working this way but the
problem is still there, everytime I convert my db I need to remove the code
so if someone has a permanent solution it would be appreciated.

It sounds as if there is something in the non convertible module that you
cannot see.
Try removing the troublesome module and replacing *before* conversion and
see if this works.

Peter

 

[Alain Vaillancourt]

I did that and the problem is still there...

It sounds as if there is something in the non convertible module that you
cannot see.
Try removing the troublesome module and replacing *before* conversion and
see if this works.

Peter

 

[ss]

scadfsafdsafds