Yes, It's actually p2ssql.dll (not pdssql.dll). This library depends on a
Microsoft SQL component, specifically ntwdblib.dll. Try adding only this
one to your client installation package.
> Hi Bunmi,
> try installing SQL Server 7 client component on the Production machine.
> "Bunmi" <Bunmi@a...> wrote in message
> > I'm using Crystal reports 7, and SQL Server 7...and its giving me some
> > headache. My report is designed on a different machine than the
> > machine...after design, I need to move the report to the production
> > and change the SQL Server name, but Crystal gives so much trouble in
> > this simple task. The problem is that when you click on the "Database"
> > menu, CR tries to access the SQL server as currently defined, and if
> > available, it takes a long while and when it gets back, it prompts for
> > server name. Normally, I would do "Set Location", and "Log on Server",
> > then point my tables to the new connection, but when I use OLE DB and
> > currently set server in the report is not on the network, then I have
> > troubles. I'm able to solve this problem by using pdssql.dll
> > Driver", instead of pdsoledb.dll but my VB6 client program fails when
> > so...saying "pdssql.dll" is not registered or something like that, and
> > can't find this file on my system!
> > Any help/ideas would be so appreciated.
> > Thanks.
> > 'Bunmi.