report import issues (2003 office)

Topic

New Reply

Hi all,

I am very confused (not unusual), I have upgraded my database with new forms and new look. I used a copy of the original to make my changes. My report however did not change. I wanted to import all of my reports to the new database. All imported except one. On this particular report, I get entries in an autosave failure table with a reason ;listed as could not open the report. If I go back to the old database, everything works fine. Has anyone encountered this problem? I have compacted and repaired both the old and new without sucess. Any sugestions?

Thanks
Kevin

Reply | Quote

Replies

We’d have to see (a copy of) the database, I’m afraid.

Reply | Quote

I think I can do that, but I know I’ve tried in the past with out sucess. It is huge and even without records is much larger than can be sent. I’ll have to zip but before I do that, could you/would you want just the reports collection or the entire tables/forms/macros/reports/queries etc. Tables are in a back end and pretty much everything else is in front end.

Thanks
Kevin

Reply | Quote

You could create a copy of the frontend, then delete all objects except the report that refuses to be imported into the new database. So the copy would contain just that report, nothing else.
Compact the database, then zip it.

Reply | Quote

Hans,

I have deleted everything except the queries that support the report and the report. I have deleted all other tables, forms, modules etc. and the zipped file size is still 206 K. Not sure what to do? Max attachment size is 100 K.

Reply | Quote

Try deleting the queries too, then use Tools | Database Utilities | Convert Database | Access 97 File Format. Specify a file name, and zip the resulting database.

Reply | Quote

Thanks Hans,

That worked and it is attached. By the way, why does 97 format reduce the size even further?

Reply | Quote

Apparently, the report Weighted Guidelines is severely corrupt. Although I can import it into another database, any attempt to do anything with it either doesn’t do anything at all or it results in a message that the object “Weighted Guidelines” cannot be found. I fear that you will have to recreate the report from scratch.

One of the reasons that an Access 97 database is smaller than its Access 2000 or Access 2002/2003 counterpart is that Access 2000 and later support Unicode (2 bytes per character instead of 1 byte) while Access 97 doesn’t.

Reply | Quote

Hans,

Thanks for your help. I might be able to go back in time to a point at which this was created about 8 years ago in access 97. Do you think there will be any issues importing fom a 97 to 2003 database directly?

Thanks Again
Kevin

Reply | Quote

You can import database objects directly from an Access 97 database into an Access 2002/2003 database without first converting the database.

Reply | Quote

Hans,

I was able to go back to a Office 97 version of this report and was able to import what appears to be successfully. However, (and I think this is related to the original corruption), I continually get a “Missing Module Error” when compiling. It seems to be related to the old binder reference in the old database. I get a can’t find/missing reference to “MSBDR9.OLB”. No matter what I do I cannot clear this error. The actual reference is no longer available in the libraries because the new machines we have did not upgrade Office but did a fresh install of 2003. So now I am at a point where the database will not compact and repair nor compile. Any sugeestions?

Thanks
Kevin

Reply | Quote

Open the database.
Select Tools | References… in the Visual Basic Editor
Do you see any references starting with MISSING near the top of the list? If so, clear their check boxes. Then click OK.
Does this solve the problem?

Reply | Quote

OK, this is strange to me. When I look in the database that I imported to, there is no “Missing” reference. When I look at the database imported from, there is a “Missing” Reference. I cannot simply uncheck/check because the file doesn’t actually exist on my computer that I am aware of. I tried browsing for it from the reference dialog and cannot find it. I presume this is because it does not come with the office 2003 software.

Reply | Quote

I’m getting lost. If there is no missing reference in the database that you imported to, where does the error occur?

Reply | Quote

I got an error which pointed to the “MSBDR9.OLB” when I initially imported the report I started this thread with (it was a copy of a database that was converterted from 97 to 2000 to 2003). The import was not successfull and it automatically created a table for autosave failures with an entry record that said it could not open the report. After posting the issue an deciding to try to import from the 97 database, it seemed to import OK. Then as I was making changes to the report to fit the requirements of the current database, and tried to compile, I got a “Missing Module” error. As soon as I got that error I could no longer compact and repair or finish compiling. If I just import the file from the original database (97) and don’t make any changes to it, I don’t get any errors. Does this help?

Reply | Quote

When you try to compile the code and get the error, is any line highlighted?

Reply | Quote

Ironically, a vba module opens up (it is a different one every time) and no lines are highlighted.

kevin

Reply | Quote

Could you zip either the Access 97 database with the original report, or an Access 2000 or Access 2002/2003 format database into which you imported the report (this database can be otherwise empty) and attach the zip file?

Reply | Quote

thanks Hans, see attached

Reply | Quote

The database that you attached is completely empty – it doesn’t contain a report.

But it does have a broken reference to the Microsoft Binder 9.0 Object Library. You can clear the check box for this reference in Tools | References in the Visual Basic Editor. The error message won’t reoccur after that.

Reply | Quote