Rich,
>
>Thanks for the reply. I am trying to now use the RDC automation server. For what reasons are using the older automation server rather than the RDC?

I started with CR 6.0 in which the RDC automation controler did not exist yet. Further on in CR 7.0 the advantages of the RDC automation over the older one are not that many. So i did decide to stick with the old one until the RDC has developed further. Now the enhancements of the RDC automation approach are significant I'll try to make the switch (though many things are the same and the switch would not require that much) whenever I'll get my CR 8 copy (I will not available before mid march up here ;-( ).

>I was using the ActiveX Viewer Control when the keyboard would lock up. I have since learned about and played with the Automation Server.
>
>I am also using VFP 6.0 and I was using CR 5.0 with VFP 5.0. However, the CR 5.0 designer was crashing so bad on my box that I gave up on it then.
>
>I am looking to add a new object in my Framework to work with and manipulate CR 8.0 in VFP 6.0. I'll search again on your posts and see what I can find.
I have already done some query results into a cursor and then took and use COPY TO FOX2X from the cursor to a temporary table to then use CR 8.0 report files against the table. That seems to work OK. I don't enjoy the problems with having to work with the report designer with temp files.

One approach that can ease the pain is to make a development version of the tables:

COPY TO ArtDev FOX2X

Develop your report based on this DBF file.

In your program:
cFile=SYS(2023)+"\"+"_"+SYS(3)+".dbf"
COPY TO (cFile) FOX2X

and change the database location to this file. (you need a reference to the report object)

oReport.Database.Tables.item[0].location = cFile

If for some reason the structure of the DBF changes, make sure you change the artDev.dbf also, and fire the 'verify database' menu option in the CR designer (database menu) to prevent nasty OLE errors in runtime.

Regards,

Walter,