Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Opening a crystal report
- Thread starter CleoMan
- Start date
Richard,
If memory serves, Crystal Reports can be compiled into EXE's. You can launch these from your Paradox applictions with the EXECUTE ObjectPAL statement. Be sure to use the complete pathname of the .EXE and don't forget to double the backslashes (e.g. c:\\mypath\\myexe.exe).
I believe Crystal also provides an OCX and some sample Paradox forms that use it. You would need to register the OCX on all client machines running your application.
I also remember that you may need to copy some Runtime DLL's onto the target machines as well. In the past, Crystal has allowed developers to install the entire Crystal package on target machines, provided you delete the CRW.EXE afterward. This provides the runtime environment, but removes the ability to create reports. Crystal has previous said this was within their license guidelines.
I'd verify this with any documentation provided with Crystal. If you can find this, perhaps there's something in the files that have been installed.
Sorry I can't be more clear, but I'm afraid I don't have a recent copy of Crystal available to me. I think there's something in my archives, but I've recently moved and my archives are still a bit of a mess. I'll poke around and see what I can find.
In the meantime, I hope this helps...
-- Lance
If memory serves, Crystal Reports can be compiled into EXE's. You can launch these from your Paradox applictions with the EXECUTE ObjectPAL statement. Be sure to use the complete pathname of the .EXE and don't forget to double the backslashes (e.g. c:\\mypath\\myexe.exe).
I believe Crystal also provides an OCX and some sample Paradox forms that use it. You would need to register the OCX on all client machines running your application.
I also remember that you may need to copy some Runtime DLL's onto the target machines as well. In the past, Crystal has allowed developers to install the entire Crystal package on target machines, provided you delete the CRW.EXE afterward. This provides the runtime environment, but removes the ability to create reports. Crystal has previous said this was within their license guidelines.
I'd verify this with any documentation provided with Crystal. If you can find this, perhaps there's something in the files that have been installed.
Sorry I can't be more clear, but I'm afraid I don't have a recent copy of Crystal available to me. I think there's something in my archives, but I've recently moved and my archives are still a bit of a mess. I'll poke around and see what I can find.
In the meantime, I hope this helps...
-- Lance
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question