>Hello,
>
>Thank you for your answer to my previous questions.
>Thank you for pointing out the FOX2X-function but the only nasty thing from converting, using COPY TO..FOX2X, is that it takes more time to convert my real database (because it's really big (28000 records) and involves a lot of tables) than it takes to run through ODBC.
>
>I've given up speeding up Crystal and VFoxPro 'cause it just takes more time to get the job done right.
>
>I thought of another approach to get the Crystal Report done:
>I've made an executable of my Crystal Report. To do that, I had to setup the ODBC administrator.
>
>Now I let VFoxPro call the program using RUN /N ...report.exe. Isn't there a new command for running other applications within VFP?
>
>But if I install it to another computer, I need to setup the odbc-administrator again. I know Crystal can distribute the obdc-drivers and files it needs. But there are some things I not yet understand :
>
>How can I let VFoxPro take care of registering the DSN into the odbc-administrator and set the path to the databases/tables I need for the Crystal Report.
>
>Can you please help me.
>Thanks.


I still think that we have a communication problem. The prg does not copy all of your tables. The prg simply creates one cursor that is just the data needed for the report...and nothing else. Once you have the cursor, copy it to the FOX2X table. The crystal report will use only that one table...and no more. This way, no ODBC is required...and fox will produce that one table faster than crystal can run the ODBC command to select the data needed.