>>If the problem was with the generated p-code then recompiling in newer revision of the compiler fix the problem. If the problem is in the p-engine then using newer revision runtime should correct the problem. I'm inclined to believe that the many of the problems were with the p-engine -- so running with the newer runtime should fix the problems w/o requiring a recompile.
>
>Yep. Except it's not an option - the customer's IT staff can't be trusted to keep two geese drawn on paper, not to mention to distribute an update to _all_ the workstations. So this one bug had to be worked around, instead, by using code which doesn't use any SP2 features. That was the easy part; the tough part was determining the cause.

Probably might be a good idea to have something in the software that identifies the runtime library version (e.g. in the application "Help/About" screen) -- might make spotting such situations a bit easier.

And on the topic of clueless IT staff... If I could get a dollar for each IT person that I had to walk through basic tasks like checking access rights to a network folder...