Thanks Dragan,

my app is an old SBT accounting derivative so everything is adhoc and bolted on.
By the implied suggesting below would no doubt solve many many problems not related to this thread.

>>Drew Speedie was famous for saying "Tricks are for Grids".
>>Are tricks also for "Set Procedure To"?
>>This is anecdotal admittedly, but twice in the last year the mere act of setting procedure to MyProgram Additive has "shot me in the toe" (so to speak).
>>In one case merely setting procedure caused an immediate corruption of a table. This was repeatable.
>>In another case merely setting procedure to MyOtherProgram additive caused a running form to close.
>>i can't possible count how many times i have set procedure to xyz program since 1994.
>>So what is it i don't know about "Set Procedure"? Much i am sure.
>>
>>Dumb as a post here
>
>Don't have any clues, just ghosts of some previous memories... not even that. Causes, explanations, nada.
>
>The one thing I was left doing was to do all my set procedure thingies in the launch of the app and not touch it later. There was a centralized place somewhere in the app's startup sequence, something like "do SetProcs" and probably also "do SetClasslibs" too. Which was all done before any tables were open. Why did I end up doing it that way? Dunno, perhaps doing all those directory searches while there weren't too many entities with their internal paths in the memory yet, before the app even tried to use any of them. Didn't have such problems since, but then can't be sure whether I had them previously or not.