Hi,
I have installed Crystal 10 and now I can see the reports I made in Maximzer Crystal embedded version.
I am having a problem the SQL Views that I had available in Crystal Embedded with maximzier are not available with the Crystal 10 standalone that I installed.
I did a verification of the address book but that did not help. I still cannot see the views that I use in the reports so my reports are giving me null values.

Please Help

Are you sure you're using the same DSN as before?

Yes, same DSN and the connection to the database is successful. I have some reports that donot SQl views and they are working fine but the ones that I use the SQl views for are giving me the problem.
I get the error saying that the "database is updating" and then gives me a null report.

Please advise..

Which database backend - Pervasive.SQL or Microsoft SQL?

Which version of Crystal 10 - Standard or Professional?

Database- Pervasive SQL
and it is Crystal full Developer Editiion

Have you tried creating a brand new report under Crystal 10 that uses the MAP_AddressBookName DSN to pull data from the address book database? Can you see the views from there?

A while back I tried installing CR10 Developer on a machine with Maximizer Enterprise 8 and it broke Maximizer's embedded version of CR. IIRC the error was "Invalid Report Creation Keycode". It may be that CR10 can manipulate its own reports but not the ones created by the embedded version.

I agree, I do get this error also if I try to run the reports from the embedded version.
How was your experience with SQl views though?

>How was your experience with SQl views though?

I just tried it again:

CR9 (embedded) broke as before. CR10 itself (Advanced Developer, typical install) works fine. I can see the views in the MAP_AddressBookName DSN, join them by Client_Id and Contact_Number, and report on them. I can even open a report created by the embedded version and run it without incident. Opening the existing report may have silently upgraded it from CR9 (the embedded version) to CR10, which might render it unusable in CR9 if changes are saved, but CR9 (embedded) is already broken so I didn't worry about that too much.

Yes. Some of the reports I made in Embedded work in Crystal 10, but the ones I used to make with views are giving me the error that the database is updating and once I check "ok" or "cancel" it gives me a null report.
I cannot even "browse data" in the SQL views.
Very confusing as to why the SQL vies cannot be read by Crystal 10 Standalone.

1. So what happened when you created a brand new report in CR10? If the views are not visible in there then your DSN is broken. If they do appear then your existing report is the culprit.

2. Have you tried using

Database > Set Datasource Location

and "Make New Connection" to reset the link to the DSN in the existing report?

I tried that and updated all the tables but still getting the same freaking error.
Very upsetting.
Are you still using the Crystal 10 stand alone with Max or are you sticking with the Crystal Embedded.

>Are you still using the Crystal 10 stand alone with Max

No.

This is the answer I got from Maximzer Corp:

Crystal stand alone version 10 is not supported since Maximizer uses a different version of the Crystal Reports engine.
A workaround would be to get an earlier version of Crystal Reports (8.5 or
9) that is actually compatible with Maximizer Enterprise 8.

However, Crystal Reports stand alone V10 and VXI is supported in the upcoming version of Maximizer Enterprise 9 (slated for release towards the end of this year).

Hey Gord,

Did you have uninstall Max to get rid of the Crystal 10 stand alone integration. I am asking because I removed the Crystal 10 and now when I want to run reports by using the Crystal Embedded I am getting an Invalid key error.

After uninstalling CR_10 Advenced Developer, Maximizer's embedded version of CR_9 was still broken (different error message) so I re-imaged the machine and started again. Uninstalling and reinstalling Maximizer may have fixed it, but I took the easy way out because it was a test box anyway.