This is hard to explain, but I need to have a procedure file that contains code that will be run at some point in the future that a project goes live, or at least is checked-into source control to be tested. There will be code in the current programs/forms that will reference these procedures, but should not do anything until some future point. In development, this code should run as it would in the future, but not what is checked-into source control. It has been suggested that I create "stub" procedures to handle this. I don't feel that I really have a choice in how this is done with regards to having code in source control that will not be used for awhile, so how do I do this? I have a procedure file, and when I add calls from programs/forms to those procedures, should they return .F. unless some certain condition is met? Something I don't like about all this, but like I said, I don't believe I have a choice. Thanks!