On my network (Access 97 backends on Win2k3 server and Access 2003 frontends) some clients get an error that resolves when the front end is closed and reopened....
And the error is "Disk or Network error." It is familiar: The same error that you would get if the drive mapping mysteriously became disconnected and you linked to a network drive instead of a UNC (I saw this a lot on Win 9x clients back in the day and never on my current Win XP clients). I prefer drive mappings because it is only a logon script that changes if the share moves to a new server.
Anyone have any thoughts besides jumping to UNC? I might be forced to try it in the next few days.
Notably I personally received it for the first time after I installed Windows Genuine advantage (WGA). Although I also had been away from my desk for a long time (few hours) and not read any data. The only reason I installed WGA is that not having it seems to cause windows update to dog the system on start up.
And the error is "Disk or Network error." It is familiar: The same error that you would get if the drive mapping mysteriously became disconnected and you linked to a network drive instead of a UNC (I saw this a lot on Win 9x clients back in the day and never on my current Win XP clients). I prefer drive mappings because it is only a logon script that changes if the share moves to a new server.
Anyone have any thoughts besides jumping to UNC? I might be forced to try it in the next few days.
Notably I personally received it for the first time after I installed Windows Genuine advantage (WGA). Although I also had been away from my desk for a long time (few hours) and not read any data. The only reason I installed WGA is that not having it seems to cause windows update to dog the system on start up.