>Unless it's something Access was causing. In the case of the HP drivers, there was a call being made to the printer subsystem that in turn was calling into the printer driver. The fix was to not make the call to the printer subsystem.
>
>Getting back to the SMB issue. If Access is making a call to something that is causing the issue, then not making the call (if that can be done), will stop the error.
>
>>Getting back to my original Layer N point, if Windows is blue-screening every couple of hours, there's nothing you can do in Access to address that issue other than stop using Windows.

It would be interesting to find out what part of SMB, if anything, Access is no longer using. AFAIK there have been no references to addressing the SMB issue in various Office SPs and "security" updates.

Another data point is that Alaska Software is still selling XBase++ (partly headlining the SWFox conference). They recommend modifying SMB parameters for their current 2.0 product: http://www.alaska-software.com/community/smb2.cxp