Ivan:

>>after all one can't live with sunshine and beautiful beaches every day !!!

Ever heard the expression "as sick as a parrott" <s>.

>Anyway, talked to Dave (got his support on Sunday !!!), and he showed the way to solve my multi-lingual issues.

Great.

>About the tables/local views/remote views, he thinks the best is to go remote straightly, and then, for the ones without SQL, just use the MSDE. What do you think of this approach ?

Well, I wouldn't want to bet against Dave's recommendations but, I suppose the answer, as always is, it depends. If you have a large proportion of non-SQL users, is fair of you to push MSDE on them <bg>. The Fox data engine is very fast and part of what makes Fox great. Using MSDE as your "standard" data engine would require some testing to see whether you're happy with its speed and scalability. If your standard "user" wont be running too many concurrent queries, and, your happy with the speed, then as MSDE is free, you will be no worse off and you have completely interchangeable code for a real SQL server implementation.

Personally, I think I would offer both solutions, DBF's and SQL server. If you stick to views, whether they be local or remote, I think you could easily code up a switching mechanism. However, Dave's suggestion to work with MSDE will allow you to use the cool parameterised SPT cursor and other goodies in V7 that just will not work on local views, only remote ones.

I don't think you could go far wrong with either solution. They both have merits but as I said, if the majority of my users were native Fox, I would think carefully before pushing them into an MSDE solutions just because of the few that have SQL server. Just my .02 penneth.

HTH