FoxPro OLE DB 8.0 and ADO.NET Errors

[Aras Kucinskas]

Hi All,

I can't to bring ADO.NET to work normaly with FoxPro 8 OLE DB provider and
FoxPro 6 data tables. Error ocure when I try to implement
OleDbDataAdapter,generate a simple SELECT statement, using wizard. Error
like this:
"The wizard detected the folowing problems when configuring the data adapter
"OleDbDataAdapter1. Details: Unspecified erro..."
Alike problem ocure generating a dataset from data adapter. Manualy
implementation of all data objects works better, but with some problems:
Data in my FoxPro tables is in 1257 codepage and connection string locale
parameter is set to 1063 (Locale Identifier=1063). The first execution of
command (in this case SELECT) return well coded data (with all Lithuanian
chars).THE EACH NEXT CALL RETURNS DATA CODED IN DEFAULT ENCODING (in this
case EN 1033). I tryed to turn off all ole db services (OLE DB Services=0)
in connection string, but the problem persist!
The connection string: "Data Source=\\MyServer\DATA;Provider=VFPOLEDB.1;OLE
DB Services=0;Locale Identifier=1063".

What solution can solve the problems? Maby the problem is in DataTables (v6)
and Ole DB provider (v8) compatibility?

Aras

 

[Sietse Wijnker]

Hi Aras,

VFP8 OLEDB should work with VFP8 data without problems. Have you updated to
SP1 for VFP8?

SP1 can be found here:
http://www.microsoft.com/downloads/...E6-DF6A-4695-965E-459FE5A761F7&displaylang=en

Also there's a specific OLEDB update for VFP8:
http://www.microsoft.com/downloads/...58-7a94-4ae1-a59e-965869cb3bc9&displaylang=en

The OLEDB update is older than SP1 and there were some changes in SP1
regarding OLEDB, so that's probably the best choice.

HTH,
Sietse Wijnker

 

[Aras Kucinskas]

Thank You for solution, but it does not help. My provider is up to date and
version is 8.0.0.3117 and now VFP8 SP1 is installed.

Interesting fact:
Custom connection parameter "Locale Identifier" value can not be saved when
creating a connection to FoxPro database from VS server explorer. After
changing and applaying changes it still remain default 1033!!! In this case
Lithuanian characters are displayed wrong, because they need 1063 setting.
This test is made on dabase created with VFP8.

Maby my method to read not EN data from FoxPro table is wrong? Maby you know
another one?

 

[Anders Altberg]

Are the tables marked as codepage 1063?
Have you got a UDL file with Local Identifier 1063?
What is Collate set to?

VFP9 should be released in a publiocbeta next week. There's probably an even
newer VFPOLEDB.DLL included.
-Anders

 

[Aras Kucinskas]

The Codepage is 1257 Baltic.
I don't use UDL file.
Collate is set to "Machine", but changing it does not influence result.

At this moment adapter, connection and dataset works well except encoding. I
develop a test app. On button click event data from FP table are populated
to dataset and dataset is binded to grid. The data is filled WELL when I
press the button first time, each next request returns wrong coded data.

There http://arosoft.voras.lt/etc/err.gif is my app screenshot with result
of 5 requests made from table with one row filled. The first row is corect.

Thanks