>>>Are tricks also for "Set Procedure To"?
>>
>>I hate procedure files and when possible, eliminate them. I wrote about that: http://www.tomorrowssolutionsllc.com/Articles/Splitting%20a%20Procedure%20File.PDF
>>
>>>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.
>>
>>Are you saying that you had a healthy table and issued SET PROCEDURE, and without any other code running, the table was corrupted? That's pretty wild, if true.
>>
>>>In another case merely setting procedure to MyOtherProgram additive caused a running form to close.
>>
>>Again, are you saying form was open and you issue SET PROCEDURE and the form closed without any other code running?
>>
>>Tamar
>
>Thanks Tamar,
>
>I will read "Splitting a Procedure File" with great interest.
>
>1). Yes i am saying that.
>I would launch a particular form with Set Procedure as the first line in the init.
>after that line executed, the table in question was not "corrupted", but a value from the first record in the table was propagated to the REST of records.
>it took me a number of days to isolate the set procedure.
>I removed the line and used Do foo in ProcedureFoo with foo (o mage to Calvin Hsia) instead.

You traced the code and that value was propagated immediately upon issuing SET PROCEDURE? That's pretty wild. Makes me wonder if instead you were DOing the procedure file and it contained some code up at the top.


>2). Yes with a caveat.
>The form was designed to remain active so that a process could be run repeatedly.
>The process was invoked and finished but then the form closed immediately after.
>
>very odd indeed (to me anyway)

Okay, so that wasn't SET PROCEDURE specifically. It was something in the procedure file, right? Without seeing code, hard to know what happened. But I'd be looking for CLEAR ALL.

Tamar