I would tend to keep it simple. Have a good bootstrap loader to keep the local executables up to date, and use a MySQL or MSSQL back end. Take great care in writing your queries and designing your screens to minimize the amount of data coming across the wire, and cache reused data locally where possible.

Alternatively, you could consider writing your app as a web application - returning only a screenful of information to the browser client. This is a good solution if the browser has a UI adequate ro what you want to do (it's somewhat limited in this respect) - advantages are superior accessibility, minimal user training, and pianless distribution.

>Hi all,
>I have written a few multi user applications in the past and need to go through a new one now. I doubt what is the best and fastest way to do it.
>The best way to my understanding was and is that the server will do all the job, keep all the data and programs and will only return the result to the station/client. The way I did it was to compile a very small application, which will keep only the menu and small table to register the server mapped network drive and give it to the client. Upon pressing any of the menu items, Foxpro will issue "do form myform.scx" or "do myprogram.prg" and return the result. Is it the fastest way? or maybe I should compile all the programs within the application (or EXE) and give it to the client? Or maybe there is another way, of which I don't know about?
>It is quite a big program with quite a lot of applications and big database, so reducing network traffic and enhancing speed is vital, as may of the reports will not only collect data, but also manipulate it in many ways.
>
>Thanks for your help and support.
>I find this site wonderful, and the people here are fantastic.
>
>Jonathan Feldman