>In the form the crystal report ocx is added with its action property set to 1
>so as to print the report in vfp application. It used to work in vfp5.0a but
>doen not in vfp6.0.The error it gives is:
>OLE IDispatch exception code 0 from CrystalReport:Invalid report file name..
>Isn't vfp6.0 compatible with crystal reports 6.0?
>If it is then why is it giving the error? The report file is there and the path
>is also correct.

Do you mean that you're adding the control when you want to print, or that you're adding the control at design time and changing the Action property to 1 when you want to print it?

In any case, Seagate recommends that you not use the OCX any more: support will be dropped in a future release. Try creating an automation server.

loCR = CREATEOBJECT('Crystal.CRPE.Application')
loRep = loCR.OpenReport('MyReportName.rpt')
loRep.PrintOut()