Thanks for your suggestion Craig, unfortunately, as we allow power users to create their own crystal reports that draw data from our database and can be accessed by other users from our app, using a local cursor or table is not an option.

I am stuck with the OCX. Placing the data locally accessing from vfp app with ocx is fine, data on the server accessed from Crystal is fine, data on the server accessed from the vfp app with ocx is slow.

I conclude that if ODBC were the problem all three situations described above would be a problem.

If it is a networking protocol problem of some sort both the second and third situations would be a problem, which leaves me scratching my head.



>>I am accessing a foxpro database via ODBC out of Crystal Reports (v 6) on a Win95 machine, my database resides on a NT server. The response is decent.
>>
>>When I access the same report, same data, on the same machines with the same DSN out of my VFP 5.0a program which uses the Crystal Reports OCX control, speed is dismal.
>>
>>I am stumped as to why there should be a difference in speed. Any and all suggestions are welcome.
>
>Probably a difference in how Crystal handles things in the designer as opposed to the OCX. I use a PRG in FoxPro to create a report table that has all the data needed for the report, then save to a FOX2X table. Crystal can read this natively. This means no ODBC setup, less support, and much more speed.