>>I found a Performance Culprit - by process of elimination!
>>Performance Issue Solved -
>>I re-made the form with all Objects (control-linked).
>>Testing seemed good.
>>Added Code - testing seems good.
>>Now Changing the Forms Properties -
>>found that Modal is slightly slower that Modeless.
>>(I’ll go modeless - need a Menu anyway).
>>When I added the PICTURE that’s when I lost Speed.
>>(I’ll do without the Picture!!!)
>>Are there other Caveat’s I should be aware of?
>>
>>Next Question: Now by making the form modeless,
>>when I exit that form -
>>the app terminates
>>
>>Process is as follows -
>>Startup Code
>>* Do Form Main, read event && FOUNDATION
>>** Button on Main = Do Form ParChild, read event
>>** Exit Button on Form ParChild = thisform.release, Clear Events
>>* Clear Event && FOUNDATION
>>Cleanup Code
>>The foundation read for the main form is Cleared w/o permission.
>>
>>Thanx - Ed B
>
>Ed, glad you've found the problem. Where did you have that snail-like picture? I'd be interested to know.
>
>As for your latest problem, Clear Events should be in exactly one place: When you are closing your App in your ON SHUTDOWN code or in your original MAIN.PRG AFTER everything else is done.
>
>If you need an example, let me know.
>
>Barbara
WOW - OK only One Read/Clear Event!

Next Question -
What’s the best way to limit data access depending on First 2 char?
All P<--->>C keys (CC9999) start with
‘MD’
‘ST’ or
‘TD’
no filter for top management - AS IS would be fine!
Maintaining about 1650 recs having 126 fields combined (includes 2 Memo).

A) Create index filtered on both parent and child & use as relation.

B) Delete DBC Relation and Create 3 View with it’s own D E.

C) Create 3 Form’s (ignoring DBC relation) having own relation’s.

D) A better way not mentioned above?
Should I be starting a new thread for each question?
Thanx - Ed B