But somewhere before the end of the program it's getting changed, and you can't imagine where. After I've found the errant code, I remove the trigger from the database so it doesn't end up in my production application. A related suggestion is one I use in VFP 6.0 when I find unexpected values in custom properties, or local variables populated from them. It isn't always obvious where to set a breakpoint to capture the exact moment when a value is in scope and is being modified. You can find yourself tracing through several iterations of the same code, particularly when the Debugger is open and attempting to share focus with your running application.
Perpetual optimism is a force-multiplier.
Inc. All Rights Reserved. Use of this site or any contents constitutes acceptance of Terms of Use. Other trademarks are used for editorial and descriptive purposes and are the property of their owners.