Eric,

I have a procedures class library that is
instantiated on system startup.

My form classes are based off a parent
form with datasession set to 2. In the
LOAD event, I call oProcs.SetCommands()

I placed SET("DATASESSION") in the debugger
and traced the load event, and the when code
steps into the SetCommands method, the data
session switches back to 1 because the code
object was created in data session 1.

Now I have not tested this with a procedure
file created with SET PROCEDURE TO, but this
is the behavior I found with form subclasses
and it makes sense because the code is scoped
to the datasession.

Your thoughts?