I’m not sure this is the place to post this but…
We have an enterprise file server (city_server) running Win2K (I know, update the OS). I have placed Microsoft Access data on a shared folder where all users map the drive as F:\.
The application tracks sewer maintenance. There are numerous factions to this FrontEnd/BackEnd operation, one of which imports new work orders from the server to connected laptops (which then go to the field for inspection; back in the office for data update). All operations work fine except for the import. If I place the BE on some other win2K server and map the drive accordingly (i.e., F:\ drive) all works perfect. Our IT people have looked at this server configuration numerous times and say it is setup identical to the others including all accounts. Yet we only see this problem when accessing data from city_server. I have tried coding the app to use a UNC path vs. mapped drive. It works better (albeit slower) but still periodically bombs.
Any ideas I can pass on would be greatly appreciated.
Thanks,
SKK
We have an enterprise file server (city_server) running Win2K (I know, update the OS). I have placed Microsoft Access data on a shared folder where all users map the drive as F:\.
The application tracks sewer maintenance. There are numerous factions to this FrontEnd/BackEnd operation, one of which imports new work orders from the server to connected laptops (which then go to the field for inspection; back in the office for data update). All operations work fine except for the import. If I place the BE on some other win2K server and map the drive accordingly (i.e., F:\ drive) all works perfect. Our IT people have looked at this server configuration numerous times and say it is setup identical to the others including all accounts. Yet we only see this problem when accessing data from city_server. I have tried coding the app to use a UNC path vs. mapped drive. It works better (albeit slower) but still periodically bombs.
Any ideas I can pass on would be greatly appreciated.
Thanks,
SKK