When Sys(1104) and Sys(3050) have had no effect on memory and VFP application stability and error prevention, I have found SetProcessWorkingSetSize to be very useful.
proc CutWinMem
Declare Integer SetProcessWorkingSetSize In kernel32 As SetProcessWorkingSetSize ;
Integer hProcess ...
Thank you gentlemen! One solution that I found to improve performance and reduce errors was to do a garbage collection prior to beginning a Fox 2.6 form-paint. Sys(1104) and Sys(3050) had no effect, but I found this API very effective: SetProcessWorkingSetSize
Code:
* Begin Code
proc...
Thank you Olaf!
Actually the code is m.modified=&cEForm.modified. I was just in a hurry when I wrote that post. I have used reference to Table.Field as @TableVar..FieldName in many places. This macro of table name seems to work, but it seemed that Griff sort of suggested that with Server...
within the last year I added some code like, m.modify=@cEForm..modify I change this to an eval and it seems to work - however, the true test is letting our customers pound on it. Thanks again Griff
We have a medical provider management suite partially in OOP (VFP 6 SP5) but much of the data entry forms are FoxPro 2.6 rendered screens from metadata in flat dbfs, which are read and each object painted on the screen is from a macro-expansion. It was an absolutely brilliant design back in...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.