Ran across this when installing Crystal to a Win7 computer. Thought I'd post to help anyone else who might be attempting this.

Other Adagio modules will pop up a warning telling you that you must turn off Window's "User Account Control" in order to install to a network drive. Crystal Reports doesn't give this notice though. So if you install all the other modules via the wksetup (wksetups don't show msg either), you won't see the msg at all.

If you don't turn UAC off before installing Crystal, you'll be unable to select any of your network drives as the destination. Same for the report tables selection. You'll only have local hard drives as options.

Turn off UAC, reboot, install Crystal, turn UAC back on (if desired) and you should be fine.

Have you tried running Crystal Reports for Adagio yet on the Windows 7 machine? What happens when you create a new report...?

On the compatibility chart, Crystal Reports for Adagio is not compatible with neither Windows Vista, nor Windows 7. I believe you will receive an error message when attempting to create a new report or Verify an existing report.

I haven't given it a thorough test, but I created a couple quick reports off of AR, OE, IC, IR and they all seemed ok (could view results, links between tables worked).

But trying to link to a GL9 database produces two error msgs:

1) Unrecognized Adagio/Accpac database
2) Library "pdbbtrv.dll" cannot be opened.

I was thinking this might have been a report table issue, but if there are known compatibility issues, I won't spend much time trying to resolve.

Any plans on a compatibility patch?

Hi Ryan

The first error message indicates that the version of Adagio Ledger stored in the GLGLOB file was not found in a local database selector file in C:\windows\crystal. You need to reinstall Adagio Ledger (90B). The file P2IRSSI.CFG should be dated July 21, 2009.

The second error is likely a symptom of the first error.

I don't have an answer for Vista / 7 compatibility.

That solved both errors, thanks!

As far as I can tell in a half day's usage, Crystal is working fine on my Win7 64bit machine.

It's installed to C:\ with the report tables set to network drive, in case that makes a difference for anyone else.

Crystal had been crashing more and more frequently right after getting the splash screen showing the Crystal Reports for Adagio logo (when trying to link to any adagio GLOB files).

I've been able to solve this problem by creating a shortcut to "C:\Program Files (x86)\Seagate Software\Crystal Reports\crw32.exe" (remove the "(x86)" if you're not 64bit) and then setting this shortcut to "Run as Administrator", as shown in attached screenshot.

I haven't had a crash since.

Hope this helps any other Win7 users.

This "Run as Administrator" option is no longer required. I was able to achieve the same success by modifying the permissions of two DLL files:

C:\Windows\SysWOW64\SSIPRT32.DLL

C:\Softrak\System\SSIBMD32.DLL

By giving "Full Control" of these files to my user, I'm now able to use Crystal without running it as administrator.

Update:

Came across similar issue at a Server 2008 based Terminal Server client today.

Only users who were part of the "Administrators" group could properly run Crystal reports. All other users would have Crystal crash immediately after attempting to link to the ??GLOB file. In this case, reconfiguring the security on the 2 files above was not enough. I had to give Full Control to the entire C:\softrak\system folder.