>No, not rot. It's an OS change. My point is, if there were a VFP team, they could add code in VFP to handle the issue.

That's the definition of software rot that I remember: nothing changed in it but it malfunctions because of the changes in the underlying OS and system API.

OK, it's been at least a decade since I last looked up the definition; the current definition cites this as one of the major causes of rot, but not the only one.

>>That's not a language bug, it's software rot. It hit any ISAM tables equally, including Access.