I have a form with notebook and several child tableframes.  There are
also memo fields outside of the TF.  Ending edit while editing a
specific memo field will cause Pdox to wink out.

On 6/9/2020 11:06 PM, Kevin Zawicki wrote:
> thanks
> 
> I do have large tables, (not large by SQL standards). But they are mostly
> tall and thin.
> 
> 
> Some of the times if is not a GPF but Paradox winks out.
> 
> I am leaning toward a certain form that has a notebook object.
> When it gets focus or arrives on the tab, several objects update. The most
> complex one was changed to SQL.
> 
> I have several other posts, it almost seems like moving source code to win7,
> running OK, then move to win10 and fails.
> 
> There is definitely something unusual happening.
> 
> I would suspect a corrupt form, BUT in runs like a clock in win7.
> 
>>
> usually due to problems with Index's - more than 50% full - and or 
> <
> What does that mean? I rebuild and compact often.
> 
> 
> I am at a loss.
> 
> In my other post I described how I moved the function to a new form and call
> that form. When the new form closes (after doing function perfectly), the
> calling form crashes.
> 
> 
> Robert MacMillan <macfam@bigpond.net.au> wrote:
>> Kevin I have not had any GPF's for a long time and have been running 
>> Windows 10 from shortly after it came out. When I was having them it was
> 
>> usually due to problems with Index's - more than 50% full - and or 
>> tables pushing the limits and or complex index's with multiple fields 
>> and field types.
>>
>> Just a couple thoughts.
>>
>> I still have problems with memory leaks and queries and that issue has 
>> been documented for years but they are not GPFs.
>>
>> On 8/06/2020 11:55 PM, Kevin Zawicki wrote:
>>> Made a separate thread, see 'WIN10 GPFs not on WIN7 - MORE"
>>>
>>> Anyone has any thoughts on the BDE settings, the sharememlocation one?
>>> I followed most the guidelines, Prestwoods notes, etc.
>>> But the sharememlocation is always blank on all my machines.
>>>
>>>
>>> I thought I saw a set of formulas for some of these seatings based on
> RAM,
>>> etc.
>>>
>>> While encountering these GPFs, I watch the task monitor, Paradox never
> really
>>> spikes on any thing, often seems low usage.
>>>
>>>
>