>No idea. I don't know what the VFP code looks like. However, years ago there was a bug in HP printer drivers that cause VFP reports to fail when printed. It also affected Word and some other products. HP refused to fix it, so the VFP team implemented a fix. So, it's possible that the SMB issue could be resolved in VFP.
>
>Do you think the Office team just told all the Access users to turn off SMB? I doubt it.
>
>>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?

We have seen this in the past where FPW2.6 was not supported anymore and fast pentium CPUs caused problems, there will be solution one way or another.
I'm not sensitive to playing the FUD card on EOL products. It most often is done out of other motives than it is a
realistic scenario.

As far as the HP bug, there was a workarround quickly. Also the Vista combobox problem was a temporary annoyance but nothing more than that.