Kevin,

If you are using ODBC VFP tables in Crystal Reports then you have to run the ODBC Administrator under the Control Panel in Windows and set the path/directory to the same path/directory that Crystal Reports is using to access your DBs/tables. If ODBC is your problem, then run the Administrator, choose Configure and VFP tables and then set the tables path/directory. I can't remember the exact choices inside the ODBC Administrator, but you can follow your nose and set the path/directory and then Crystal should be able to find your VFP tables.

This also relates to saving the choices as a DSN name. A fellow UTer named Bernhart Milcent sent me a reply on 2/14/02 and on 2/15/02 that shows how to set up VFP form to pass DSN information to Crystal Reports on the fly rather than running the ODBC Administrator for different Crystal Reports that use different paths/directories. Crystal Tech Support told me I would have to set up as many different DSNs as I had different Crystal Reports using different tables in different locations. DSN1 might be for c:\myfiles\mytablea. DSN2 might be for c:\yourfiles\mytablea. Different location requires separate DSN name. Otherwise, you would have to run the ODBC Admin program each time before running Crystal to set the right path/directory prior to running the VFP/Crystal combination.

Bernhart showed me how to pass the DSN information to Crystal similar to the way I pass parameters from VFP to Crystal. Hope this helps. I haven't tried Bernhart's code yet, but I will in the near future.

If you're not using ODBC, then all bets are off. I don't know what to tell you.