>Two obvious ones - first change the MEMLIMIT to a maximum of 15500, and >second, adjust the .PIF of the FPW app to run in its own address space >rather than the shared Win16 address space.

Co-incidentally, I have a similar problem just cropped up with a client upgrading to XP and a fast machine.

I already have emailed him the patch for that and that is OK. However they are now getting low memory errors which causes my error trapping to restart the app (with a prior warning about low memory) in the middle of trying to enter data into a text box.

I will try to get them to edit the Config.fpw, but I don't know about a Program Information File for FPW2.6a, or is that a "local" Config.FPW you are referring to?

All suggestions gratefully received.