>>I have a small, 82K byte VFP 6 .exe that queries a number of tables to produce a cursor for data export. It is running on a PC where it is called by another program that is running as a service. The tech from the company that produces the CALLING program says that when I first installed my exe it ran fine. However, it is now running very, very slow. He says that if he runs it directly it runs fine. However, when run from his program it runs very slow. He says that my VFP program, when called from his, is being running as a service by his program.
>>
>>He says that, according to the process list under the Windows Task Manager my exe is only using 2 MB of RAM. My first thought here is that when it is run as a service that somehow the memory is being severely limited. Because of the size of the tables that are being queried I would expect that it would be using at least 6 or 7 MB.
>>
>>Anyone got any thoughts on this?
>>TIA
>
>There is no direct correlation between table size and memory used.
>How do they start your exe? Could you ask them to use ShellExecute for this purpose?

Edward, based on what I have seen with other queries I would expect at least 6 MB and would not be surprised to see it well over 10 MB. Most VFP apps take well over 2 MB just to run without a query.