Actually, it was items 1 - 9 in the synopsis of the problem that I thought might be relevant to you.
As for p2sodbc.dll, it should be installed in the windows\system32 folder. Crystal shouldn't be able to connect to the db without it, if you are actually using odbc to connect to the...
Take a look at this article. It may point you in the right direction. It's for CR 7, but the technologies used in CR 7 and CR 8 are similar. Sorry I can't give you a better answer, but you're using an older technology I can't model, so I'm limited in what I can suggest...
First, I think we're talking apples and oranges, because the parameters you can create for command objects (i.e., within a command object) cannot be a Range type (at least it can't in CR 9). They can only hold a single value. If you've created a Crystal parameter, you can only use it in the...
Often, this sort of problem is a rights problem. The account that runs the application must have rights to SQL server. Also, verify that the ODBC connection is properly configured on the dev box and can be seen by the account that runs the application.
Are you using the Automation Server...
I think you'll need to post your entire sql command in order to get a reasonable response (I assume you mean the SQL statement in a Command object you've created in CR 9). Also, although your odbc error message includes a reference to Access, it's usually helpful if you provide info about your...
Where are you trying in your code to pass the parameter? I don't see any reference to a parameter field object in your code. Try downloading the sample vb apps at the Crystal Decision website. They will point you in the right direction...
Well, if you are actually pulling back 494,934 records to the report, then 32 seconds is pretty good performance. Your performance sounds like it is the best it is going to get. You are suffering from a bad database design (from a Crystal perspective, at least).
Pervasive db's, particularly if they are based on old btrieve files, are very sensitive to the use of indexes. (And if you are using ddf files to access the btrieve files, the ddf's need to be designed to accurately reflect the btrieve indexes.) You can get incredibly fast performance if your...
What you need to do is use the PrintingStatus object along with the ReadRecords method. Prior to calling the PrintOut method, do the following:
Dim crpPrintStatus as PrintingStatus
Set crpPrintStatus = crpReport.PrintingStatus
crpReport.ReadRecords
If crpPrintStatus.RecordsRead > 0...
I'm not clear how the subreport is working in your report. Is it displayed in the main report? Or are you using an on-demand subreport? The sample you gave looks like it's just the data in the main report, based on your description of your grouping.
And, how are you deploying the report?
Yes, you can import an existing rpt file into the designer in vb.
When you add the Crystal designer to your vb app, you get a "Report Gallery" dialog. On that dialog is an option to create a new report from an existing report. Select that option and then locate the rpt file in the...
So you actually have no record selection formula in the report itself (there is no WHERE clause in your sql query). How many records are being returned to your report?
Please clarify one other thing. Are you using an OLEDB connection to the Access database or are you passing an ADO recordset...
The PDF export dll for CR 8.0 was, at one time (prior to the release of v. 8.5), available from Crystal Decisions at their website. However, upon release of 8.5, they pretty much abandoned support of PDF export for CR 8.0. You might try searching the Crystal Decisions KB for info on 8.0 PDF...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.