>>>VFP used to have a problem with the vast amounts
>>>of memory typically available in NT environments
>>>forcing us to use SYS( 305?) to limit FG/BG memory.
>>>
>>>Is this still an issue with VFP 6?
>>>
>>
>>It depends on what you mean by 'is it an issue?'
>
>The "issue" is that VFP has a problem handling all of the
>memory available to it in an NT environment. Consequently when
>running commands that act on a table enmasse (SQL SELECT, DELETE FOR,
>COUNT FOR, etc), VFP will eventually stop responding.
>
>You have to limit foreground and background in order to avoid this
>problem.
>
>My question was does this problem still exist in VFP 6.0

I haven't seen this, working with some very large tables, with both NT Server and NT Workstation. But, then, I didn't have the problem with VFP 5.0a; if you're talking about the message that VFP is not responsing when running a single, processor-intensive, command (such as very complex SQL Selects) then yes, but the problem comes from the fact that VFP doesn't respond to Windows events within the context of a single, atomic step - if you have a SQL Select that takes 10 minutes to run, other events don't get responded to, such as timer firings, or standard Windows messages. But that is not a memory issue, and it is not limited to NT.

>
>> If you need to load other stuff, or have multiple VFP serssions, or especially if the NT box is acting as a network server as well as running a VFP app, then toning down VFP's appetite is a good idea.
>
>Yeah, I thought the same thing. It would be nice if
>that's all there were to it
>
> ...kt