I always had better luck pushing the data into SQL Server. We'd push it into a temporary database, audit it in SQL Server, then append it into the permanent tables. HTH.
-Kevin CULLY Technologies, LLC [email protected] wrote: > Greetings Friends! > > I need your help! I am in Puerto Rico working on a situation with a client > that has been causing problems for us for a while. We have been importing > VFP created .csv file records into a M$ SQL Server database with success > overall, until a recent output change added a new field. Most records will > import, but within the first few doaen records, seemingly at random, the SQL > Server import process will choke indicating a structural problem. Upon > examination we have concluded there is no structural problem with the data. > It "feels" like it is a SQL "goofism". > > Amyway, I proposed to get around that issue we try to use ODBC to connect to > the VFP7 tables, which are contained in a .dbc. The SQL Server 2005 tools > include a Linked Servers feature, but I have not been able to get connected > to any of the tables, much less to the .dbc itself. > > Have any of my esteemed associates (that's y'all) had anya experience with > this kind of connectivity to VFP7 tables within SQL Server 2005? I stand > ready to receive your responses, and happy to have the help. > > > Kindest Regards, > Gil Hale > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
