Hey Mike,

Yes it is weird. My original code did include ADDITIVE. I keep thinking it's because I moved code to another machine, but even when I create a new empty .prg it blows up. Machine 1 was under source control, so I made sure that the .prgs were not read only and I recompiled all .prgs and .vcxs. I'm sure I can work around it, but it's always frustrating when it works on one machine and not the other. That's what I always tell my boss anyway, 'It works on my machine!' :)

John

>Hi John
>
>That's weird. SET PROCEDURE has nothing to do with a table. Unless somehow the .PRG file is actually a DBF? I'd think you'd want to SET PROCEDURE TO .prg ADDITIVE so you're not accidentally closing other open procedure libraries.
>
>>I moved some code and classes to a different machine and am having a problem. I am using a 'SET PROCEDURE TO myProcedure.prg' statement in the above method of the DE. This code works fine on machine 1 (VFP 7 SP1 - Win XP). When I try the same code on machine 2 (VFP7 SP1 - Win 2000) I get the error 'Not a table'. I have tried creating a new form and a new procedure file. Even if the procedure file is empty I get the same error. Drop the SET PROCEDURE statement and the form runs fine. It even will execute other commands in the same method.
>>
>>TIA
>>
>>John