Chuck

That's great

All I was doing was explaining the object that will use the SQL-Server data...

I'd like to keep using the COM object just point it to a different data store not rocket science but for me NEW....

jp




>>OK,
>>
>>That's very very cool
>>More info is required from me I guess.
>>
>>I created a COM Based ('Query Runner') descriptive LAME NAME I know but what it does is it take the parts of a SQL Statement and Macro Subsitutes it and brings back data to a Server Based Temp File that the user has a reference (NAME) to.
>>
>>Effectively it run's a query generated on a client at the server and drops a temp file in a user visible directory...
>>
>>NO UDPATES, DELETES, or any data manipultion is required at all just (GIMME the data) I control how long the temp files live and such so this might be very posssible
>>
>>I'll keep bothering you
>>
>>thanks
>>
>>
>>jp
>>
>>
>
>I guess I don't understand exactly what you are asking. A linked server in SQL is basicly SQL Server hitting FoxPro
>
>Here's how you set one up with Enterprise Manager
>In Enterprise Manager, click to expand the Security folder.
>Right-click Linked Servers, and then click New linked server.
>On the General tab, follow these steps:
>In the first text box, type any name for the linked server. What ever you want to call it.
>In the Server type text box, click Other data source.
>In the Provider name drop-down list box, click Microsoft OLE DB Provider for Visual Foxpro
>In the Data source text box, type the full path and file name of the FoxPro DBC.
>Click OK to create the new linked server.
>
>Now to query it.
>You could select * from linkedserver...foxpro_table
>
>I have only did this once and it was over a year ago. If I remember we had to setup some security on the linked server to get it to work correctly.