In general, layer N code can't "handle" issues with layer N - X code other than by avoiding use of that code. How could a newer version of VFP avoid the use of SMB?

>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 not a language bug, it's software rot. It hit any ISAM tables equally, including Access.
>>
>>>Flip side: Existing language bugs don't get fixed.
>>>
>>>I'm trying to thing of old things in .NET that were renamed. Can't come up with any,
>>
>
>
>None of these are .NET things. They're OS items.
>
>>Well well... who'd a thunk. And that being a flagship product from a company which renamed
>>
>>- directory into a folder (after refusing to call it a folder all the way into 1995, because that's what it was called on Macs and Ataris)
>>- windows explorer into file explorer (both serious misnomers)
>>- system tray into notification area
>>
>>There's more, but it was a long day. Can't remember.