p2p.wrox.com Forums

Need to download code?

View our list of code downloads.

  Return to Index  

crystal_reports thread: Re: Changing the SQL Server name using pdsoldeb.dll

Message #1 by "Rene Franco" <r_f_1972@y...> on Fri, 5 Apr 2002 07:22:05
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.
> regards...
> "Bunmi" <Bunmi@a...> wrote in message
> news:61319@c..._reports...
> >
> > 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
> production
> > machine...after design, I need to move the report to the production
> machine,
> > 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 
> not
> > 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",
> and
> > 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 
in "Convert
> > Driver", instead of pdsoledb.dll but my VB6 client program fails when 
I do
> > 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.
> >
> >

  Return to Index