Hi all, I apologize in advance for my windyness.
I've been experiencing problems with some parts of my apps working in my office and most of my customers, but not in a few of the others. I've mentioned this before and the fact that sometimes adding a few blank lines at the top of the offending command file sometimes solved the problem. Yesterday I had the same thing come up, and sun-of-gun, when I added trace to the top of the file the problem went away (although trace didn't start under runtime). So I commented out trace, codelocked, sent back to the customer, and it still worked. Today I realized I was kidding myself because I use RClass to prepare for codelocking and I have it set to strip out comments. So I removed my comments (leaving the file the same as when the problem occurred), codelocked, sent the files back to the customer machine, and everything worked fine. In the past I've solved problems just by re-codelocking, but thought those instances were just flukes... I think I was wrong. It seems that codelock hiccups on occasion. So I'm wondering if there might be a coding style or some other practice that might help assure the apx files coming out as expected? But also; why would a single version of a codelock run differently (successfully and not) on two machines. And, I still have one routine that has worked perfectly at a half dozen sites, but not at one other (this is over the course of two years and many revisions)? Ben Petersen
