Eons ago, I inherited a large procedure app, and ran into this:

Several of the functions in the procedure file began with the same 10 characters with a couple of characters at the end discriminating the function.
VFP sometimes executed function AAAAAAAAAAXX when the program called function AAAAAAAAAAYY.
It drove me battty for a few days till I figured out what was going on.
I never figured out the logic of why it worked sometimes and not others.
I changed the names so that the first few characters were unique and the problem went away.
Just a thought.






>>>I've inherited an application that uses a procedure file. I've been making changes for a couple of weeks with no issues, but today, my changes aren't being applied. Specifically, I modify the code in the procedure file, and run the app again (from the Command Window) and the change doesn't show.

I've tried all the usual things: delete the FXP and recompile, check for other versions that might be getting used, etc. In fact, I stuck SET("PROCEDURE") in the Watch window to confirm that it's what I think it is.

Here's the really weird part. I set a breakpoint ("FUNCTIONAME"$PROG()) to stop execution at the top of a particular function. When the breakpoint fires, I use ASTACKINFO() to see that the right file is being called. Not only is it, but the line it shows me in ASTACKINFO() is the changed code. When I step through it, though, it executes the unchanged code.

A couple of times today, though, it behaved. Seems to me that's when I'd made larger changes, but I can't see how that would matter if I actually delete the FXP and recompile.

I've tried shutting down VFP and restarting it, too. The only thing I haven't tried is rebooting.

Any ideas?