On Wed, Nov 12, 2008 at 2:15 PM, Paul Hill <[EMAIL PROTECTED]> wrote: > On Wed, Nov 12, 2008 at 11:03 AM, geoff <[EMAIL PROTECTED]> wrote: >> yeah tried that no difference. Just as well I wil be using VFP to >> export to SQL and not relying on this. Ive tried it on a vista >> machine as well and it actually kills VS2008! just goota be something >> else. Thanks for the help! > > A nice way to export data from VFP to SQL is to simply generate the > SQL INSERT commands into a text file (TEXT..ENDTEXT could be handy). > It's nice because you can do validation on the fields for errors. For > example, checking for invalid dates. Also, if a field is Empty() then > maybe you could write a NULL. > > Make sure you write a 'GO' every 100 records or so. -----------------------------------------------------------------------------
SQL Server will pull into the DB faster than you can insert away from an outside client. for 2000 there are DTS jobs and for 2005 there is SSIS. <http://tinyurl.com/5oyn5p> for data import in 2005. -- Stephen Russell Sr. Production Systems Programmer Mimeo.com Memphis TN 901.246-0159 _______________________________________________ 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.
