Right.


I already do that, completely. Even have a grouping layout.
Fully qualify all methods and only ones called in form or lib from other
libs.

There was a recursing compiling issues where you had to recompile one of
the libs twice.

If A calls B that calls A, on open I think.



There was a thread here...   "Magic Screwdriver".



Tom Krieg <REMOVEtomkCAPITALS@sdassociates.com.au> wrote:
>You can, of course, overcome all of this recompiling forms and libraries

>nonsense if, in your uses clause, you specify individual methods rather

>than a library name. It's more tedious and requires more documentation 
>(Documentation? What's that?) but will save your hair in the end. You 
>can modify a library method and if the parameters don't change, you 
>don't have to recompile anything except the library. And you can add new

>methods and so on.
>
>For example
>Uses objectPAL
>  ;// Library apUTILS
>  GetUserInfo() dyAny
>  PassMemo(mToBePassed memo)
>  ReadMemo() memo
>  ;// Handler Library methods
>  HandleMethod(var dynRequest dyAny) dyAny
>  ;// Called form methods
>  NewModel(liBrand longint,var stError string) logical
>  GetRetailer(liRetailer longint,var stError string) logical
>endUses
>
>
>On 18/05/2020 7:40 pm, Tony Spencer wrote:
>> I keep getting unexpected general protection violation when running some
scripts
>> can anyone help please
>> 
>