>>I only have one slight problem preventing that. I already have a client who has designed several reports for this application and all of the reports are based on VFP5.0. I suppose I can look to see how easy it will be to convert the database type. Thank you for the suggestion.
>
>
>I'm not sure you understood the answer. Keep the data in VFP tables, using the DBC, etc. When you run the report, use a PRG to extract just the data needed for the report, then COPY TO Temp.DBF TYPE FOX2X. Have the CR use Temp.Dbf. Doing it this way provides a couple of advantages. 1) It will use Rushmore to pull the data. 2) You don't need ODBC to access the data, which not only simplifies installation and support, but will also be faster.

Hi Craig,

PMFJI, but this is exactly where I'm at, and I had one related question to using the FOX2X type data to avoid ODBC. (didn't even think of the RUSHMORE advantage...what a bonus!)

From what I understand so far, I do need a table or view to design my report in CR, so in order to create the proper environment for my CR report design I should:


1. run the select I'm going to use in the real app into cursor.

2. copy that cursor to a FOX2X table that will be the same name as the table that is going to be created in the real app.

3. Now I can design my report?

Is that how the design process should go (basically) when using a FOX2X table, or am I thinking about this all wrong?

Thanks for your time.

John.