A
Antony_cts
Dear All,
I am wondering can ADO.Net export/convert to (Foxpro)DBF?
Regards,
Antony
I am wondering can ADO.Net export/convert to (Foxpro)DBF?
Regards,
Antony
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
M
Miha Markic
ADO.NET won't do anything like that.
Perhaps you might read data into a DataTable and save it into DBF but it
won't create a new database for you.
Perhaps you might read data into a DataTable and save it into DBF but it
won't create a new database for you.
W
William Vaughn \(MVP\)
No. ADO.NET can extrude XML but no other database formats. However, it can
connect to DBF databases or any database with an OLE DB or ODBC (or .NET)
driver/provider.
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com/blog/billva
http://betav.com
____________________________________________________________________________________________
connect to DBF databases or any database with an OLE DB or ODBC (or .NET)
driver/provider.
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com/blog/billva
http://betav.com
____________________________________________________________________________________________
K
Kenny
Antony ... I'm pretty sure an export to an older dBase III format would be
simple to code ... in fact I prolly have the code laying around somewhere and
would be happy to share if you need it.
And ... I think that foxpro could still read that ...
The only tricks I can think of would be things like long field (column)
names, numbers of columns and datatype translations.
Exporting something like a table with 10 or 20 or 30 columns (not 300) of
"limited size" character and "numeric" fields should be a snap.
But ... I'm just talking from memory ... I didn't get into the way back
machine just yet. {;-)
simple to code ... in fact I prolly have the code laying around somewhere and
would be happy to share if you need it.
And ... I think that foxpro could still read that ...
The only tricks I can think of would be things like long field (column)
names, numbers of columns and datatype translations.
Exporting something like a table with 10 or 20 or 30 columns (not 300) of
"limited size" character and "numeric" fields should be a snap.
But ... I'm just talking from memory ... I didn't get into the way back
machine just yet. {;-)