Trial version Crystal Reports 2008 and Access 2007

[Former Member]

Hi,

I just downloaded the trial version of Crystal Reports 2008. I am using Access 2007 and Windows 7. I can open existing reports (created in an older version) and modifiy them. However, if I try to add new tables or create a new report, the program (Crystal Reports) stops working. When I check the error log, it referes to crw32.exe. From reading other blogs, my guess is that there is an Access/Crystal Reports disconnect. But when I try to open an older version (2003) of Access, I still get the same result. My version of windos 7 is 32 bit, not 64.

Any help would be appreciated.

Lisa

[former_member11696 · Accepted solution]

Hi Lisa,

Convert your reports to use OLE DB or ODBC to Access then they will be forward compatible.

Thank you

Don

[Former Member · Accepted solution]

Don,

Thanks for your reply. I went in to the "Save As" to try what you suggested, but not sure how to proceed. The reports were created back in 2003, and the company does not own a copy of Crystel Reports. I downloaded the trial version and was able to open the reports and overwrite them with the current format (is this what you were referring to?) I can save,modify and print the reports, however, when I open Database expert to add new fields from tables that were not originally linked to the report, I get an error message "Crystal Reports has stopped working". I have read all the posts in regards to compatibility issues with Access 2007 and CR 2008. I have tried downloading the AccessDatabaseEngine.exe, choosing the OLE DB option in the Database Expert and everything works up to the point that I am selecting tables to link to the report. Everytime, it fails. The program shuts down. I wasn't sure if this was user error or maybe the trial version isn't as robust as the full version. I had also read that CR2011 would solve this issue. Thanks for your assistance.

Lisa

[former_member11696 · Accepted solution]

Hi Lisa,

A few things to be aware of. It could be the reports were older than CR 9 version so the database drivers all changed. Saving then with CR 2008, which is a full feature for Trial versions, it just stops working after the timeout happens, may break the old reports if you over write them. So save as to another location etc.

Without much details on the original reports I can't suggest next steps.

Try setting location to your Access database without adding a new table or field just to verify that much still works. Then save as a new report, close the old report, open the new report and then try adding another table/field as well as link the new table.

Thank you

Don

[Former Member · Accepted solution]

Don,

Thanks for the quick reply. Not what I was hoping for. The reports were written in v8.5. I tried what you suggested and received the error "Details: ADO error code0x80040e4eSource:Microsoft OLE DB Provider for ODBC Drivers. Description: Operation Cancelled." I also tried to just start from scratch and create a report making the connections from the beginning. I choose "Create a new connection, 1. OLE DB (ADO) then 2. MS Office 12.0 Acces Database Engine then 3. Datasource - choose the database name 4. Type: Access then click next and finish. CR stops working at that point. Makes it sound like user error to me. Not sure where I am going wrong. Either way, I am not able to make a connection.

Thanks for your help, even if it doesn't achieve the desired results.

Lisa

[former_member11696 · Accepted solution]

Hi Lisa,

Does the access database file have a .mdb or .accdb file extension?

Try using the MS Jet driver for access and see if that works.

Thank you

Don

[Former Member · Accepted solution]

Don!

I think I had a break-through!!! The database had an .mdb extension. It was oringinally created in 2000. I have Access 2007 and had opened the database and resaved it as a 2007 database. I had been working in it for about 2 months. When you commented on the age of the original CR reports, I started thinking about the age of the database and the drivers. I went in to Access and created a test database, saved it as .accdb. I then went in to CR and created a new report and linked the tables in the newly created database. It worked! Now I supposed the real dilemna is getting the database updated. I thought saving it as a 2007 version would be sufficient, but apparently not.

Thanks for your patience and help through this frustration process. Oh, by the way, it also worked with the older reports that I had saved in the new format, I was able to link the new table to the reports. The probelm seems to be with Access and not CR. I need to hammer away on that issue now.

Thanks again,

Lisa

[former_member11696 · Accepted solution]

Great news.... The problem is with the JET driver, CR 8.5 would likely have used the Native ADO connector, CR 2008 updated both the driver and dependencies. Possible MDAC 2.8 may help you if you don't have it, belongs to Microsoft.

Also, CR 8.5 has no inkling what a accdb file is so the driver conversion likely caused the crash.

I any event, upgrade the driver and the reports and it should all continue to work without issues. Just one word of warning, due to the age of those 8.5 reports you may have to rebuild them from scratch using the copy paste options. You may not but because of their age there may be an update issue the the Developers have not encountered.

Thanks again

Don

PS - please remember to mark posts as answered when you are done...