"Not Supported" - Distributing VB6 Program w/ CR 7

[skillo]

Anybody seen this one before?? Whenever I try to view a report on a client machine that doesn't have Crystal Reports installed, I get this error message.
According to crystaldecision.net they said that the p2sodbc.dll was found to be an older version on the client's machine, in other cases. I have checked this dll along with many others and the versions match what I have on the development computer. I'm about to pull my hair out. Any suggestions??
Program is in Visual Basic 6.
A report out of Crystal Report 7 was imported to be used with the Crystal Smart Viewer.
Everything works fine on the development computer. Just not getting something right in the distribution.

 

[balves]

Did you build a Windows kit using the VB Package and Deployment Wizard? It should pull in all of the u2*.dll and p2*.dll files that you need, based upon the references selected in VB. Brian J. Alves
Terrier Consulting, Inc.
Email: brian.alves@worldnet.att.net
VB / Crystal / SQLServer

 

[skillo]

I did use the Deployment Wizard & as far as I can tell it is including all the u2*.dll's and the p2*.dll's. I have used the dependency walker to view all the files that are depended on and as far as I can tell they are all being included. I have looked through Crystal's Runtime Help Files and have included anything that was there and not in the deployment wizard. I did find the crpe32.dep file that Crystal claims to have all the runtime files included that VB needs and have packaged that. As soon as the client computer becomes free I am going to try and uninstall & re-install to see if that clears up anything.
Thank you so much for your help!!! and if you think of anything else I can try holler back!!
I have a feeling that something important isn't getting registered, but I would hope that a more informative error message would be displayed.
Thanks again!!!!!

 

[balves]

What about the version of the ODBC driver on the client system? Does it match the version on the development computer?

I would search the whole C: drive of the client system for p2sodbc.dll. Perhaps there's another version from a 3rd-party tool or older install of Crystal. Brian J. Alves
Terrier Consulting, Inc.
Email: brian.alves@worldnet.att.net
VB / Crystal / SQLServer

 

[skillo]

Ok, Here we go again!! Finally got tired of it last night and went home. I have checked the ODBC driver and it's the same version. I did do a search and it's the only version of p2sodbc.dll on the machine. The next question I have, though, is: Does the version date have to match what's in the dependency file? For some funny reason the date on the compressed dll file(i.e. p2sodbc.dl_) off of the CR Installation disk, comes across with the correct creation date of 6/21/99. But when it uncompresses the file during setup it sets this creation date to 4/5/01. Do you think this will hurt the way it processes, being that the dependency files are referencing one created on 6/21/99?? I know it's pretty far fetched, but I'm getting pretty desperate!!!
Thanks again for your help!!!

 

[balves]

The Setup.Lst file generated by the VB Package Wizard tells you the datetime stamp of each file in the kit. Compressing the DLLs should not change the datetime stamp during the installation on the client PC.

The CRPE32.DEP file tells VB where to get the files. Some could be in \Windows\System (or \Winnt\system32) and some could be in \Windows\Crystal (or \Winnt\Crystal).

Perhaps it's your development PC that has the multiple copies of DLLs.

I'd try another client PC to make sure it's the kit that doesn't work. DLL Hell can be a painful experience. Brian J. Alves
Terrier Consulting, Inc.
Email: brian.alves@worldnet.att.net
VB / Crystal / SQLServer

 

[skillo]

Going crazy!! Last night I ended up deleting all the p2sodbc.dll 's off my development computer(which was 2 that had different creation dates - dated here in April) and uninstalled Crystal Reports. I Re-installed, hoping this would fix the dates, but they came back on with 4/5/01 as the creation, and 4/5/01 as the last modified. That's when I quit!! I did finally track down an article on CrystalDecisions this morning of someone having a problem w/CR version 8 and the p2sodbc.dll. They suggested deleting the dll, and Expanding it straight off the CD and on to the C drive (with the command prompt). I have done that on my PC and it did fix the dates, so now I am waiting for the client PC to be free (probably lunch) and I will do the same to it.
Do you think the date would really cause this much of a problem even though the version is the same?? If it does, I am really going to laugh about all this!!!

 

[balves]

We're running Crystal V8 Developer's Edition. The file p2sodbc.dll is Version 8.0.0.84 and has a date stamp of 1/27/00.

Deleting a DLL from Windows Explorer does not remove the Registry entry for the DLL. It's better to un-register the DLL, then delete it.

If you have deleted a bunch of DLLs, but not un-registered them, you might want to pull down the Microsoft tool called RegClean and run that on your PC. RegClean will clean up the registry to match your C: drive. Brian J. Alves
Terrier Consulting, Inc.
Email: brian.alves@worldnet.att.net
VB / Crystal / SQLServer

 

[skillo]

Ok!!!
Will do that. I don't know anything about the window's registry, but am learning a little at a time. I sure appreciate your help!!!