>Craig,
>
>For the short term this is unavoidable. Ultimately the whole thing will be reworked and the reporting will be either in SSRS or Crystal. But for now, the reporting is only part of it. I know it sounds backwards, but, for now, we are taking a badly written Access application with a SQL backend and pushing the data back into dbfs.

You could just do the reports in SSRS w/o changing anything else in your Access or VFP processes.

SSRS reports are straightforward to set up, and are more flexible than VFP reports.

>
>>Perhaps you should rethink how the reporting process is done. Is there a reason it has to be from DBFs?
>>
>>>I have a program that gets data from sql server and puts it into vfp tables (free tables). From there reporting is done against the dbfs. This needs to be done multiple times a day. One table, tblactivity, has about 500K records.
>>>
>>>Regarding the following code:
>>>lnr=sqlexec(lnh,"select * from tblactivity","curactivity") && takes 30 or 40 seconds
>>>copy to tblactivity_vfp && takes a few minutes?? haven't benchmarked exactly, but it is slow
>>>
>>>Is there a way to speed this up? Years ago I used BCP, don't remember much about it right now, but thinking it would speed up writing to a text file, but then I'd have to append into a dbf anyway.
>>>
>>>Is there any way to bypass sending results to a cursor first, a way to use sqlexec to go straight to a dbf?
>>>Any way to speed up the copy to?
>>>
>>>Thanks.