For us it was a memory problem in Client 32 and Novell has no plans to fix it. The fix is to switch to MS software, but I don't make that decision, so I cope. No biggie for me since I keep everything open all day.

There are a lot of frustrations in this business, and they can get to you sometimes. Me, I'm Polish, and we're genetically optimized for beating our heads against walls. ;>)



>>During a busy day, and after launching and closing many apps, I go to launch FPW 2.6 and my system freezes. It's the ONLY program I have that does that???? One of my associates has the very same problem. Has anyone else experienced that? Are there any known fixes?
>>Thanks
>>Harry Marks
>
>This problem has been around for years since VFP5.0 as we are converting 2.6 to now 6.0. I concur with the memory hog analysis. If you open VFP once or twice after a fresh boot before you open 2.6, you can generally forget bringing 2.6 up. If it is a memory flushing problem after VFP closes, why can't M$ fix that? Given the overhead that my machine has in the bootup procedure anyway, it would make life a lot easier if we could work with a tight operating environment.
>
>Well. . . .glad I got that off my chest.