An Override stays in effect for all programs further down the call stack from the point it was issued. So If A calls B and B issues and override then calls C. C will see the override. A will not. Be sure to have B delete the override when you are done with it, as a matter of good housekeeping. There are a lot of little exceptions and twists to this. Are you using Shared open data path? If so, once the file is open, no override will make any difference. Are you using ILE activation groups? That will affect which overrides are seen by which programs. Use the general rule shown above and if the behavior doesn't seem to be working as expected, then let us know and we can dig into your specific situation. Or go ahead and post some code so everyone can see the specifics of your situation.