>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.
>
>
>

Not necessarily. When you launch CR Designer and make the connection for the report, the connection is made then. To get new data, it is just a requery. When you use the OCX, everything must happen...the connection must be made, the data queried, and the report printed. The slowest part of this will be making the connection.