Luis ---

5.0 no produce los nombres de meses en ingles? Y 6.0 no puede traducer los nombres en las funciones? Que malo. Penso que es major para usted a esperar por 6.1.... o algo.

>There is an extremely wrong thing with VFP 6.0 that I never thought I coulb be on any version. What happens is that I develop in the Spanish version of VFP 6.0, well all the functions and messages that are related to the language are ok (for example: CDOW() returns the day in Spanish like "Lunes", "Martes", and so on; CMonth() returns "Enero", "Febrero" and so on) but when I make an .exe and run it as standalone (I mean, I don´t run it from VFP but from the Win desktop) all the values that functions returns are in ENGLISH!!! so Cmonth returns "January", "February" and so on, that´s absurd! other people have complained the same. So when is MS going to do something really fine? They are the bigger in software but I think they have come to a point where they don't care to do a quality software they just do things to have new versions every year and earn more money!
>
>Well, I will keep with VFP 5.0a that daoesn`t have this problem, I think it is the best version of VFP they have ever made.
>
>>>Ok, but you also can find bunch of similar things within any version of any product. The context of issue was about stability of VFP5a against another version, and this example does not hurt it much, sorry.
>>
>>Ed,
>>
>>The issue is that VFP 6.0 is the current version adn 5.0 is a past version. 6.0 will get serivice packs and 5.0 will not. The bottom line being that anything that is a problem in 5.0 will remain a problem forever, while problems in 6.0 will likely get fixed.