Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Importing problems
Message
 
To
24/09/2002 17:44:44
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Miscellaneous
Thread ID:
00703929
Message ID:
00704169
Views:
23
Dragan,

I would like to try an other option. At this moment I create an instance of Access for the export. I want to try to open the database with Ado and copy it data directly into the VFP table. This means I'm not exporting/importing data anymore....
If this does not work I will look into your suggestion.

Thanks for the input.

Ron

>>I´m trying to import data from Access and I have run into a small problem
that I have not (yet) been able to solve.
>>For my applications translations need to be made for different languages (Hungarian is the latest). This translation database is written to Access.
>>Having completed the translations the file is returned, I check its contents (in Access) and if nothing weird is located the file is imported into VFP.
>>
>>In VFP I create a Access-object, open the database and export the file to a dbf. This dbf is then imported into the VFP database.
>>This worked fine...until the Hungarian language came along.
>>
>>This language has an i without the dot on top.
>
>It doesn't, it has a regular i and long i (see lower).
>
>>When examining the Access file I can see this character, having exported the data to dbf this character is gone, it has been replaced by a normal ´i´.
>>I have tried in VFP to play around with the codepage but the problem is created by Access-export (2000).
>>
>>Can anybody help me with this. I don´t won´t to tell my customer that he has to copy all text from Access to VFP by hand (because this works without any problems).
>
>Access is probably keeping Hungarian text as Unicode, while in VFP you need to have your tables set to codepage 1250. You can do this with
>
do (home())+"cpzero\cpzero" with "your table.dbf", 1250
>Do this on each table which holds Hungarian text. Still, that may not be enough. You may need to tweak other things (depending what your Access object uses as transport mechanism) to convince it to use proper setting. If you're using W2k, you may need to set the Hungarian locale as default and reboot, to tell Access the system setting for the conversion is Hungarian, or else it may keep converting. Also make sure you have the support for Central-European languages installed, your fonts should be about 150k or more, and you should have 1250*.nls and *1250.nls files in your system directory.
>
>Besides, the "hosszú i (looks like í in ISO-8895-2)" (long i) has an acute accent on it. You'll also notice the lack of double acute accent on some O's and U's (often found as the last character in a word).
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform