>Ref..Foxpro 2.5 DOS database by default Codepage 850, Machine Collate.
>
>Thanks to José and the others for your replies.
>
>It helped me to solve at least most of the problem.
>
>Summary of what I tried:
>From VFP5;
>USE PART
>DELETE TAG NOM
>SET COLLATE TO "GENERAL"
>INDEX ON NOM TAG NOM
>COPY TO PART2.DBF WITH CDX TYPE FOX2X AS 850
>(if we don't mention the 850 it is changed to the VFP5 default 1252 and the accentuated caracters are then changed in the transfer. Ex. é becomes ú, etc..)
>CLOSE DATABASES
>
>USE PART2 ORDER NOM
>...great result. The order sequence is now Ok.
>CLOSE ALL (and QUIT)
>
>From DOS;
>USE PART2
>...error "File not open"
>
>To José;
>Foxpro 2.5c is for the Mac. Right?
>I am on PC and Foxpro 2.5x is not sold anymore anywhere.
>
>The proposed solution to the client
>I suggested to solve only the Windows (VFP5) part since all the reports are there...and that we don't know how much time it would take to solve the 'problem' if we ever solve that problem.
>-----
>(beside you and me): he is a very good customer but he doesn't want to pay for this language problematic. He says that it should have been already in the system by default and so on... Who knows how much more time I would have to put in that to find the DOS solution. I already spend almost a day as cumulative time in tries/tests and so on.
>-----
>
>The solution for now
>Here is what I found with my tests and your suggestions.
>
>I can leave the DOS database untouched.
>
>In VFP5, I just added SET COLLATE TO "GENERAL" at the very first program of the chain called INTRO.Prg
>
>Result
>The DOS browsed indexed on NOM is not better than before but at least it is untouched and there is no danger of "unexpected" results and tedious time consuming research to find what would be wrong + the client's frustration.
>Actually it is sorted like this in DOS;
>Beaulieu
>Brassard
>Bruchesi
>Bérubé
>
>(Bérubé should be right after Beaulieu)
>
>With SET COLLATE TO "GENERAL" VFP5 reads and show the DOS database PART (indexed on NOM) in the good sequence. So most of the problem is solved for now.
>
>If anyone has more solution I would certainly appreciate since we could (maybe) run into the DOS problem in the near future since we began selling to Europe.
>
>Thanks to all again.
>
>======================================================
>>>We have an application where we have a Foxpro 2.5 DOS database by default Codepage 850, Machine Collate.
>>>
>>>This database is read and we make many reports with VFP 5. We must deal with french accents like é è etc... If we do nothing, the order tag does not position the names with the accents correctly. It is the first time we must deal with accents.
>>>
>>>Is there a very simple way to make everything works fine in DOS and in Windows.
>>>
>>>Thanks in advance

Real,

I checked my archives: 2.6a is the latest DOS version. I've read here several times that when you own the actual product, you could get older versions from MS. But don't ask me how, I have no idea. Conversion from to 2.5 to 2.6 is a snap, so you could rebuild your DOS app to take advantage of the "new" international features of FP DOS 2.6

In any case, you should mark your PART table with Codepage 850. The fact that it has DOS data is different from the fact that every table should be marked with an appropriate codepage. That would avoid the use of the "AS" clause, and you would see your data properly from within both environments.

That's about all I can say for now.

José