>>To those who wondered why I wrote it that way - I didn't; I inherited an old SBT system that has the same procedures in a big procedure file (SBTPROC.PRG) and also as standalone files. Thanks for the help.
Depending on the version, there are several ways to deal with this.
Here's what I do:
Make copies of SBTPROC.* and save them somewhere in case none of this works.
Then erase the procedure you are modifying in SBTPROC and recompile it.
Recompling is where the versions differ. In later versions, there's a utility that you have to use to rebuilding it.
If the system has had weird modifications, none of this will work and you'll have to restore your old files.
As a last resort, I've had to rename the modified module and change all the calling modules to use the renamed module.
SBTPROC harkens back to days when hardware was much slower and in most cases it's no longer relevant.
Anyone who does not go overboard- deserves to.
Malcolm Forbes, Sr.