Hi guys,
I am generating a report using crystal report from vb6.0. I already designed the report using crystal reports with sql server 2000 as back end. when I am generating a report from vb 6.0 it giving the report error as "SERVER NOT YET BEEN STARTED". Can any please help me. Its matter of urgency for my module.
I tried using logonserver, its connecting to the server but when i tried using action = 1 to the report its giving me the error. I think its problem with the server connection. please help me out.
Re: problem(crystal report, sql server 2000,vb6.0)
Hi,
My DSN is working fine. I am connecting to my dsn with rdo and getting the values into the dsn but giving problem only when connected with sql server via vb to generate the report.
I am sending the code .
my dsn settings dsn=gghms;userid=hms;pwd=hms
report.logonserver "p2ssql.dll","192.168.20.1","gghms","hms","hms"
crviewer.reportsource = report
upto here it is fine working when used to generate the report with the action command on the report it is giving server not yet started.
cr.action = 1
Another important thing is when i designed the report in crystal reports 8.5 and saved the report with data then it is not giving any errors (since it was connected to the db at the crystal report instance) and it will loose the connection when i opened it else where again.
when I save the report without data then its giving me the problem.
Re: problem(crystal report, sql server 2000,vb6.0)
U hav to make DSN once again & it will definitely run it.....
OR
U prapare new report...make all connections with database, then & only then it will run.....Becoz i had also same problem when i had done these then its working properly...
Re: problem(crystal report, sql server 2000,vb6.0)
IMO you are intermixing code (different versions and engines of CR) to call a Crystal Reports' rpt
Please post your actual code where you are calling the rpt and say which version of Crystal Reports you are using
Also say if you are using Crystal Reports' RDC or OCX
JG
... If your problem is fixed don't forget to mark your threads as resolved using the Thread Tools menu ...