System & S/W Info :
SQL Server 7.0 on W2K Server
Crystal 8 Dev on W98 Dev Mach
VB 6.0 SP4 on W98 Dev Mach
Client PC’s W98
Background :
I have a report that I created on the dev machine that uses a registry based DSN to access some views on SQL server. I use a VB form to get report parameters from the user, which I boiled down to a simple record ID based selection formula to pass to the crystal OCX control.
Problem :
Everything works like a charm on the development PC. On the client PC’s I set them up to have the same DSN name pointing to the same server, nothing different except the PC & the user. Again all works fine except, here is the problem, the Development PC must be online on the network or else it takes about 15 seconds before the report loads. Yes, it does eventually come up put it seems that something has to time out. If my Dev PC is up then it comes up instantly.
Initially I used the connect property of the OCX then I switched to the logoninfo property. I have used the server name instead of the DSN name in my connect or logoninfo string. I made a second report that was very simple and got the same results. Nothing seems to work.
It seems to me that it has something to do with my PC name. I opened the report in WordPad and see that they do store the PC name in the report. I saw some examples of connect strings that use a WSID parameter but the Seagate examples do not show this parameter. I tried it though and it did not help.
Has anyone seen this before? Any ideas appreciated.
Bill Hudson
irobot98@worldnet.att.net
SQL Server 7.0 on W2K Server
Crystal 8 Dev on W98 Dev Mach
VB 6.0 SP4 on W98 Dev Mach
Client PC’s W98
Background :
I have a report that I created on the dev machine that uses a registry based DSN to access some views on SQL server. I use a VB form to get report parameters from the user, which I boiled down to a simple record ID based selection formula to pass to the crystal OCX control.
Problem :
Everything works like a charm on the development PC. On the client PC’s I set them up to have the same DSN name pointing to the same server, nothing different except the PC & the user. Again all works fine except, here is the problem, the Development PC must be online on the network or else it takes about 15 seconds before the report loads. Yes, it does eventually come up put it seems that something has to time out. If my Dev PC is up then it comes up instantly.
Initially I used the connect property of the OCX then I switched to the logoninfo property. I have used the server name instead of the DSN name in my connect or logoninfo string. I made a second report that was very simple and got the same results. Nothing seems to work.
It seems to me that it has something to do with my PC name. I opened the report in WordPad and see that they do store the PC name in the report. I saw some examples of connect strings that use a WSID parameter but the Seagate examples do not show this parameter. I tried it though and it did not help.
Has anyone seen this before? Any ideas appreciated.
Bill Hudson
irobot98@worldnet.att.net