In Crystal 8.5 I'm using the PDSSQL DLL for my connection from Crystal to my SQLServer2000 Database. The front end is Visual FoxPro 7.0. The connection works quite well there, however, things have changed in Crystal 9.0.
In 8.5 you could set the database location to MyServer.MyClient.dbo.MyStoredProcedure. Then, by stripping off the MyServer.MyClient, you could connect to different clients on different servers using the LogOnServer method:
g_oCRRep.Database.LogOnServer("PDSSQL.DLL", "MyServer", "MyClient", "MyUser", "MyPassword"
If you don't strip off the "MyServer.MyClient" the LogOnServer doesn't override the default.
In Crystal 9.0, I'm not finding a way to create a new report using the PDSSQL DLL. I'm trying to use that so that I can connect to multiple servers and clients without having to create new DSN connections on every machine for every server.
Any thoughts on how I can deal with this would be appreciated.
In 8.5 you could set the database location to MyServer.MyClient.dbo.MyStoredProcedure. Then, by stripping off the MyServer.MyClient, you could connect to different clients on different servers using the LogOnServer method:
g_oCRRep.Database.LogOnServer("PDSSQL.DLL", "MyServer", "MyClient", "MyUser", "MyPassword"
If you don't strip off the "MyServer.MyClient" the LogOnServer doesn't override the default.
In Crystal 9.0, I'm not finding a way to create a new report using the PDSSQL DLL. I'm trying to use that so that I can connect to multiple servers and clients without having to create new DSN connections on every machine for every server.
Any thoughts on how I can deal with this would be appreciated.