p2ssql.dll needs SQL Client, but WHAT IS IT??!!

[jfrost10]

Hi gang,

People have told me that I need SQL client on my machine for ps2sql.dll to work. But whre is it/where can I get it? Reason i ask: I have a report thats generated in vb, that pulls info from a remote sql server. However, I can do it, my collegues can do it, but our clients can't! We all have win2k installed, but we havn't installed any SQL client, unless it was in a win2k add on and we didn't know(???).
Any thoughts? The error we're getting is Can't find physical db, and if we try and register p2ssql.dll, we can't (load library error or reg svr just won't do it). Also of note, that NTWDBLIB.dll that you supposedly need? Well, I don't have it, and it still runs off of my machine. Crazy stuff!

Thanks,

Jack

 

[balves]

If you go into ODBC Administrator, in the Drivers tab, is there a driver for SQL Server, like V3.6 or V3.7?

If not, go to

http://www.microsoft.com

and download MDAC V2.5.

Brian J. Alves
Email: brian.alves@worldnet.att.net
VB / ASP / Crystal / SQLServer

 

[jfrost10]

Hi Brian,

Yes, I have in the drivers tab:
SQL Server version:3.70.08.21 name: SQLSRV32.DLL

And on our test machine (which is duplicating the problem with the clients) it has the same driver listed.

jack

 

[balves]

So you built a VB kit and installed it on the client's PC? Any errors during the installation? Brian J. Alves
Email: brian.alves@worldnet.att.net
VB / ASP / Crystal / SQLServer

 

[balves]

There's a pile of "Physical Db not found" articles. This one seems the closest:

http://support.crystaldecisions.com/kbase/c2009409.asp?AJID=811F8574E165694383032E8B8F38557F

Brian J. Alves
Email: brian.alves@worldnet.att.net
VB / ASP / Crystal / SQLServer

 

[jfrost10]

Hi Brian,

Yes, I we built a VB app that loads the reports (we didn't use designer files, straight call to the directory where the reports are kept) and displays them in a viewer. All of the location settings for the report are done in code, although the report giving us grief was created off of an OLE DB connection to the SQL server. Now, here's the catch:

This report used to be working fine (well, except for some issues with what it displayed) and now its not. The problem is we can't figure out which DLLs are different between the machines (we even installed every Crystal DLL possible on a test machine, and it STILL wouldn't run properly). I know that the p2ssql.dll has a dependency on the NTDBLIB.dll, but I don't have that one on my system at all AND I can run the report off the sql server! Too many weird things happening!

Jack

 

[balves]

Well, it wouldn't hurt to put NTDBLIB.dll on the client PC. It's probably a different version of a DLL than a missing DLL.

Some people swear by Dependency Walker:

http://www.dependencywalker.com/

Brian J. Alves
Email: brian.alves@worldnet.att.net
VB / ASP / Crystal / SQLServer

 

[jfrost10]

Very true. Is NTDBLIB.DLL located on the CR disk? Since I don't have it on my system, gotta find a copy of it somewhere. And you're right, it probably is a different version more than likely. There are so many things that install crystal dll's, its hard to keep track!

We use the Wise installer for our software, and it even installs CR dll's in our development systems. Weird stuff!

Thanks again, I'll keep you posted.

Jack

 

[balves]

I believe that NTDBLIB.DLL comes with VB. Brian J. Alves
Email: brian.alves@worldnet.att.net
VB / ASP / Crystal / SQLServer

 

[jfrost10]

Hey Brian, are these "DLL's" actually DLL's?!

I can't register p2ssql.dll with regsvr32, I can't register NTWDBLIB.DLL, and I can't register p2lsql.dll (either Load Errors or File cannot be found errors)!

Also, nada on the NTWDBLIB.DLL idea...still doesn't run on the test computer....Is there maybe something that win2k installs thats optional that has some extra sql support? Those poor clients have so many dll's on their machine, and no IT staff, so trying to get them to fix anything themselves would be nightmarish!
:
Jack

 

[balves]

DLLs have been around since the beginning of Windows, before the Registry and COM. In the old days, you built a DLL in C++ and then declared it for use in other tools like Visual Basic and PowerBuilder. You had to know the path of the DLL file, or put it in one of the standard Windows directories that everyone had in their PATH so that the VB app found the DLL.

Then with COM/Active-X, you registered DLLs and your VB application didn't have to specify where the file lived on your PC.

So, if it's a COM/Active-X DLL, it has to be registered. Otherwise, it probably does not. How do you know what kind of DLL it is? Beats me.

If you step through all of the DLLs in Project / References in VB, you'll see the file path for each one. If none of the files is P2SSQL.DLL, then it's not a COM DLL. Brian J. Alves
Email: brian.alves@worldnet.att.net
VB / ASP / Crystal / SQLServer

 

[HoustonGuy]

You need the SQL Server desktop engine installed:

You need the SQL Server MSDE for SQL Server version 7.0 or the Desktop Engine for SQL Server 2000 (version 8.0). Once this is installed you should be good to go - if I understand your question/problem.

Otherwise just install the Client Tools from the SQL Server CD if you have it.
Cody ford
Data Mining, Cleansing and Reporting Specialist
codyjford@hotmail.com

SQL, VB6, Seagate Info/Crystal Reports