Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DBase III & VB .NET & Serious Problem

Status
Not open for further replies.

digimortal

Programmer
Oct 12, 2003
28
TR
I don't know if this belongs here but it is vb .net related. If not please move my post to the correct forum.

I have 25 Dbase III tables and I created ODBC connections using MS FoxPro VFP Driver, MS Dbase VFP Driver and these 2 connections, can only see 6 tables out of my 25 tables.

The second thing I tried is creating a ODBC connection using MS Dbase driver, this time I can see all the tables but all my non-ascii ( turkish ) characters got messed up...

So my questions:
1. Correct ODBC driver to use with Dbase III files
2. I hope I can use one of the MS FoxPro or Dbase VFP Drivers, so is there a way that these drivers see all of my tables?
3. If I must use MS Dbase driver (I fear I have to...) How can I change encoding of the table from VB .NET

Thanks in advance
 
The VFP driver should do a good job of this. Are you actually planning to write an application around DBASE III tables, or are you planning to migrate the data say to SQL Server.

The tables that may not be getting opened, could be those with Memo fields, and I vaguely remember a problem with tables with blank empty date fields, though I think this is related to migration.

Also, have you tried the VFP OleDB driver?


Sweep
...if it works dont mess with it
 
Yes you are exactly talking about my problem, I will take data from Dbase III tables and send them to SQL Server and then create reports. And I can not change anything on Dbase tables because they are being used by another application.

Yes I'm importing some tables with OleDB VFP driver but "some" tables, not all of them. It seems the driver does not recognize some of the dbf files as tables.

At first I thought it could be the memo fields but some of the tables that can not be read, does not have memo fields. And I have imported a table that does have 2 memo fields.

Thanks in advance
 
When you say it doesnt recognise them as tables, what do you mean?. How are you getting them into SQL.




Sweep
...if it works dont mess with it
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top