Steve..

I received a support call on this today. I did not see relevant information on this issue on your website or on the UT.

FWIW, at line 3810 of INTL.PRG, there was a missing , between two local variable declarations. It looks like the 7 compiler is a bit more picky.

You did test the product under the beta....right? Or, you simply forgot to update your site.

As for being a MS induced bug, 4 letter abbreviations have been commonplace. With that said, I am not willing to say that new language features implementing the usual 4 letter abbreviation is a "bug". One could argue that not allowing 4 letter abbreviations would cause a lot of compile errors. And, making astackinfo work differently would be inconsistient with how other language constructs work. Then again, is this really an issue? I think not..

As you have noted, the solution does not require heavy lifting. As the vendor of what I think is a great product, and knowing that a lot of people will be compiling their INTL-based apps in VFP 7, folks will come accross this problem. I did a search here and found nothing. That is why I posted the info here - as a resource - especially in light of the rash of VFP7 related issues that have cropped up as of late...


IAC, you will probably want to update your site...