Re: Same form, but one system GPFs...?

On Thu, 21 Feb 2008 07:23:09 -0700, "Tony McGuire"
<png.paradoxcommunity@[EMAIL PROTECTED]
> wrote:

>> The "only" problem with cMax that I know is that it requires a full 
>> lock
>> which of course could be problematic on a shared table. However, I 
>> have never heard that it has cause a GPF and using it against a 
>> table in PRIV that is not being edited shouldn't be a problem. At 
>> least that is how I have
>
>Except that when the issue was presented he wasn't using :priv: - he 
>changed it later.

Hi Tony,

(and no, I am not moving in the direction of "Why does
Paradox work that way...<g>)

Just to clarify:

I had not modified anything relating to the :PRIV: in my
code.

I was trying to make any modifications is a systematic
manner, and the change of the :PRIV: was next on the list,
but I had not made that change when the GPFs stopped.

As was true when I had the frequent GPFs, right now, the
form is on the server, it has a button that runs a query,
the answer.db is local to the machine with the problem, and
that machine's :PRIV: is the default (and has 54 characters
in the path string.) 

All the best,
-- 
Kenneth

If you email... Please remove the "SPAMLESS."