We're using fox2x table to transfer data between Fox2x and VFP6 application
and Sql 2000 server. Sql 2000 access that table thru Linked Server (OLE DB over ODBC).


>I've not tried to do this before and was wondering what I need to be aware of and what I can or can not do.
>
>I'm wanting to share 2 VFP tables (WB_IN.DBF and WB_OUT.DBF) with SQL-Server. These tables would be a staging area between our in-house VFP app and a new website we're about to develop. The web user would fill-in a set of forms and submit them (after appropriate web side input validation), to us for processing. The submission process would result in multiple records being created in WB_IN.DBF
>
>My user would have a screen/form in the in-house VFP app, to bring the information from the WB_IN table into our in-house app.
>
>The in-house app would also create records to be sent back to the web site, via WB_OUT.dbf Taking the records from WB_OUT and bringing them into the web app would not be part of what I need to deal with (at least, not at this time).
>
>I was thinking of having the tables be a part of my VFP (5.0a) DBC.
>I'm not sure I need them to be a part of my DBC.
>
>Are there any advantages/disadvantages to them being in the DBC?
>One reason of having them in the DBC would be to be able to use long field names...making them more readable. At this time I'm thinking there would be any Trigger code. Would SQL-Server have any problem with these tables if they are a part of my VFP DBC? Would it have a problem with the long field names? What if I do add VFP trigger code?
>
>TIA,
>Rick Liebespach
>--------------------------