Server has not yet been opened

[Varco]

I have a Crystal V8 report compiled into VB that is running against a SQL database. A valid ODBC connection has been established and tested, however when the report runs we get the message "Server has not yet been opened". Any thoughts? Jim Varco
Varco Consulting
varco@compuserve.com

 

[StevenK]

I've seen this problem a number of times on developing applications. It may be down to one of two things :
1). The client machine from which you are generating the applicatio through the VB application does not have the database access DLL's as required (these include things like 'p2sodbc.dll', etc - for a full list see the 'RunTime.hlp' help file in the Seagate Software folder).
2). The Crystal Report is not able to access the data due to incorrect access parameters or location for data. Ensure that the application is passing the appropriate server-name, database-name, user-name and password (if dealing with a SQL Server 7.0 database). Similarly ensure that if the report is accessing different databases at run-time that the location for each of the database tables is set correctly.
Hope this leads you to a solution to your problems
Steve

 

[Varco]

Thank you for your response. I beleive I included the needed files, 'p2sodbc.dll' was one of them. There were 2 other files I had to manually add to the distribution set, SSCSDK80.DLL and CRPAIG80.DLL. The other required files as listed in the "Report Designer Component" section of the RUNTIME.HLP file were already included. This same report configured for a ODBC connection to a FoxPro database works fine, are there files specific to SQL7?

After creating the ODBC connection and testing it it looked like we have a good connection. No passwors is being used. Thoughts? Jim Varco
Varco Consulting
varco@compuserve.com

 

[StevenK]

First off : Are you working against a SQL Server database ?

Regardless of the fact that your server log-in does not request a password you will still need to indicate the log-on information for the Crystal Report database tables - indicating the server-name, database-name, user-name and password. Is this being done ?
If you are working against a database name other than the one that was developed against you will also need to set the location of the reports database tables (using something like 'CRReport.Database.Tables.Location := 'database-name.dbo.table-name'). Is this done ?

Steve

 

[Varco]

Steve, Thanks again. Yes, it is a SQL Server database. The database names are different, however I thought this was dealt with via the ODBC connection being setup with the same name for the development site and also at the users site, even if the database the DSN is set to is different at each location. Is this wrong? Jim Varco
Varco Consulting
varco@compuserve.com

 

[StevenK]

I think that you will find that the database-name is hard-coded in the report (if you open the .rpt file in something like NOTEPAD you will probably be able to find a reference to the database-name in question).
I would suggest attempting to set the logon information for each of the report database tables - using something like the following (as I do in Delphi) :
for tpI := 1 to (CRReport.Database.Tables.Count) do
begin
CRReport.Database.Tables[tpI].SetLogOnInfo(server-name, database-name, user-name, password);
end;
Alternatively in place of this combination I think you can indicate the ODBC connection name in place of the server-name (so use combination of ODBC name, database-name, user-name + password).
You may also need to set the location for each of the report tables - using something like the following :
for tpI := 1 to (CRReport.Database.Tables.Count) do
begin
if (CRReport.Database.Tables[tpI].Name = 'Table-name being looked for') then
begin
CRReport.Database.Tables[tpI].Location := database-name + '.dbo.' + table-name;
end;
// Do checks for other tables to set location for...
end;
I hope this helps in some way ...
Steve

 

[edlssi]

StevenK

I noticed your name and your problem in the Tech Tips board. I am
developing a in Visual Fox with Fox 2.6 tables... you say you have no
problem with the not connected to server error in Fox... I do...

I am in Crystal 8.5 with ODBC connection.
The data base is not a secure database. As a matter of fact the tables
I am reporting off of are created during the application run time.

I am running he p2sodbc.dll... If I save the data with the report
everything is fine.. If I turn that option off I get the data
connectivity error.... so obviously I am not getting data connectivity
at any time, just stored data.

This application is to be distributed... so do I have to somehow set a server, uid and pwd?

Sorry for the intrusion but any thoughts would be greatly
appreciated....

Edward Christianson
Lender Support