OK, I'll try that, thanks. What has me worried is that there
are other reports already in the access interface that work correctly (but don't take parameters), and which call the same print engine functions (except for PESetNthParam).
(using access 97, crystal 7.0 report generated by crystal reports 8, windows 2000)
I am trying to generate a report based on a stored procedure in an MSSQL database which has an MS Access front end interface.
At the moment I am creating the report using crystal API functions, namely:
- call...
At the moment the report itself contains the stored procedure call. I am creating the report using crystal API functions, namely:
- call PEOpenPrintJob
- <various api calls to set procedure location>
- call PESetNthParam for each parameter
- call PEOutputToWindow
- call PEStartPrintJob
-...
I have an MSSQL database with an MS access interface.
I would like to print a report on a resultset that is generated by a stored procedure on the SQL database. The report is created and works correctly. It is set up to take a list of parameters and pass those to the stored proc.
How do I...
-...
I have partly solved my problem in the post "printing groups then detail". In order to display the group headers before the detail I group within my query and return a very wide dataset containing both summary and detail columns. In the summary rows the detail fields are all null, and...
I have a report with 3 levels of grouping. Is it possible to print group bands (headers and footers) for the first two groups first on one page, and then the detail bands (grouped by group 3, the innermost group) surrounded by header and footer starting from the next page?
Example:
Detail record...
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.