drosenkranz
Programmer
I have a FoxPro 6.0 form with 3 command buttons- each launching a
report. Theform has been running fine until I added the line "Set Printer To
Name ...". trying to direct the report to a specific printer
After that, I started receiving an error message: "OLE lDispatch exception code
0 from CrystalReport: can not open SQL server..." whenever I attempt to
launch one of these tryed and tested reports.
Removing the line does not restore the ability to run these report s any longer
either. This had occurred once before during development and was fixed by
deleting the OCX from the form and replacing it with a new one. It didn't work
this time. Seagate even cautions users not to change the properties on the
OCX but to make any and all changes through code which I have held to.
Does anyone have any info on why the OCX behaves so poorly with
FoxPro? Thanks. [sig][/sig]
report. Theform has been running fine until I added the line "Set Printer To
Name ...". trying to direct the report to a specific printer
After that, I started receiving an error message: "OLE lDispatch exception code
0 from CrystalReport: can not open SQL server..." whenever I attempt to
launch one of these tryed and tested reports.
Removing the line does not restore the ability to run these report s any longer
either. This had occurred once before during development and was fixed by
deleting the OCX from the form and replacing it with a new one. It didn't work
this time. Seagate even cautions users not to change the properties on the
OCX but to make any and all changes through code which I have held to.
Does anyone have any info on why the OCX behaves so poorly with
FoxPro? Thanks. [sig][/sig]
