MS did make some changes to SMB from the time the issue was originally reported. If Access users are no longer reporting problems, I suspect one or more of the following:
- Those changes fixed the issues Access users were seeing
- Access users are applying SMB registry mods just like VFP users
- Access users are living with the issue like many VFP users
>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?
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
