>I have a client who has installed on one (networked) computer a total of 4 VFP apps, all accessing the same database which is elsewhere on the network. Two of the applications are sizeable (.exe's of 1.7mb and 2.4mb which exclude any report definitions) and are often - but not always - run sumultaneously. The other two are smaller (202K and 50K) and are run at various times. Ultimately, these two will runn all the time, with timers to initiate actions (uploading or downloading data from the internet via INET controls).
>
>The two main applications are used by others on the network.
>
>My question is: would it be better to:
>
>a) Roll up the applications so that they are effectively one (not an ideal choice)
>
>b) Have applications called by other applications using RUN commands
>
>c) Have them all individually started from the Start menu
>
>d) Have a 'wrapper' application which can call any or all others
>
>e) Any other ideas?
>
>I feel that the machine (it has 64Mb of memory) might hit memory problems with 4 separate VFP programs running at the same time.
>
>As an addendum to the question, other users have the two main systems, and report their machines slowing down as the day proceeds. Should I consider limiting the memory space (some way??) for each exe?
>
>I would be grateful for any advice.

---

Almost without exception VFP apps should be using SYS(3050,1) and ,2 to specify VFP's memory useage - left to its own devices VFP tries to use everything in the machine. A patent nonsense, the VFP team should of had this little gem highlighted (in a tip of the day) each and every time that a developer starts VFP! Considerable performance increases are possible (but not guaranteed) if you adjust this setting. Four apps should be no problem what so ever. So your best implementation route is up to you.