>>>Another tip - in 2.0 the reports were already tables (in 1.0x they were the
>sa
>>me, but saved as text delimited with TAB), so they may be corrupted. Try reop
>en
>>ing them in the editor, do any minor change (add a space behind some text and
> d
>>elete it) and save; it should force cleaning 'em up or blow up on any bad one
> -
>>but at leas't you'll locate it that way. Sometimes Using the .frx and packin
>g
>>helps also.
>>
>>Thanks for your reply Dragan. I inherited this application so I have been bui
>ld
>>ing standalone exe files as that is what had been done in the past. There is
>an
>>extended version of 2.0 but the exe was always built as just standalone not
>st
>>andalone extended. This may have been because not all of the workstations wer
>e
>>capable of running the extended version in the beginning but now they all are
>.
>>I am going to try building a standalone extended exe and see if that makes a
>di
>>fference. I am wondering though how much the other programs each workstation
>ha
>>s affects the performance of Foxpro. For example each workstation runs Window
>s9
>>5 and Word. Several others have other programs as well such as an accounting
> a
>>pp, CADD, or Excel. Will using the extended version of 2.0 interfere with the
> r
>>unning of these programs? Thanks again for your help. I will be glad when the
> a
>>pp has been converted to an oop windows application!
>
>For mixed environments, the solution (recommended in help) was to
>build compact exe, and install both 16- and 32-bit (extended)
>runtimes, and have the loader decide which one to run. It decides on
>the amount of expanded/extended/dos memory; try to run
>
>fox -v
>
>and it will tell you which one it thinks it will run. This way, the
>same exe may run on extended runtime on some machines, and on
>overlays on others.
>
>As for the resources, Fox/Dos with an extender always took all the
>memory it could get; I've noticed significant delays at load time
>each time I've doubled the memory. It takes more time because it
>initializes all this memory and partitions it for buffers, string
>space, house chores, internal bookkeeping and all the other
>misterious stuff; the more you give it, the longer it takes, but
>then it runs considerably faster, buffering and caching all the
>things it can. Under Win95 it will take as much memory as it needs
>or finds; it may affect your virtual memory usage. You may edit the
>settings for the .pif, by limiting it to 8 megs (sounds reasonable),
>but in general it works fine by default, and fiddling with tweaking
>is mostly a waste of time. You may notice a delay in other apps if
>FPD does heavy data crunching in the background, but fox itself
>shouldn't be delayed by other apps' memory usage (it already took
>what it needs), unless the machine is heavily using virtual memory.



Thanks for the reply Dragan. I have another question maybe you can help me with. I used to be able to access help (for foxpro) but it just wouldn't work one day. I get an error message about insufficient stack space. I didn't change anything on my pc so I don't understand why all of a sudden I got this error. Do you have any ideas on how to get help back? Thanks again. I will let you know how I make out with the memory problems after I try a few things.