(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 PEOpenPrintJob
- <various function calls to ready the database>
- call PESetNthParam for each parameter
- call PEOutputToWindow
- call PEStartPrintJob
- call PEClosePrintJob
PEOpenPrintJob is returning a jobnumber as expected.
There are 10 parameters to the procedure, and PESetNthParam is returning true (working correctly) for each of these.
PEOutputToWindow returns true.
*but*
PEStartPrintJob returns false.
Given that the only variable parameter to PEStartPrintJob is the jobnumber, and given that this jobnumber has been used successfully in all API calls from PEOpenPrintJob, I do not understand how PEStartPrintJob is failing. The report window appears on screen for a fraction of a second, then disappears without an error message.
T.I.A.
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 PEOpenPrintJob
- <various function calls to ready the database>
- call PESetNthParam for each parameter
- call PEOutputToWindow
- call PEStartPrintJob
- call PEClosePrintJob
PEOpenPrintJob is returning a jobnumber as expected.
There are 10 parameters to the procedure, and PESetNthParam is returning true (working correctly) for each of these.
PEOutputToWindow returns true.
*but*
PEStartPrintJob returns false.
Given that the only variable parameter to PEStartPrintJob is the jobnumber, and given that this jobnumber has been used successfully in all API calls from PEOpenPrintJob, I do not understand how PEStartPrintJob is failing. The report window appears on screen for a fraction of a second, then disappears without an error message.
T.I.A.