WLAN now being set up in office.. what to do with my database

[munkee]

Hi all,

I am currently making live a database I have created in access 2003. There is the possibility of 5 concurrent users at any time (a lot more users overall though). This was all being handled correctly by splitting the database and distributing out the front end.

Now our site has just received an email regarding a wireless network being set up within the office. From my previous research all I can think is this is a very bad thing for my poor database due to the possibility of corruption.

Wireless is notorious for dieing mid connection so am I right to be worried about the possibility of corruption most days if employees are asked to switch over to wireless?

What can I do to reduce the possibility of corruption?

Regards,

Chris

[MMcCarthy]

OK I've actually dealt with this issue recently where the client had a mix of hard connections and wireless.

As long as all the users have their own executable (mde/accde) version of the frontend on their local drives you shouldn't have a problem with corruption. Worst case scenario you just have to replace the frontend file.

We did find a couple of times that the lockfile for the backend file on the server couldn't be deleted as the database had been locked open by a couple of the wireless users. This was only a problem when we were doing upgrades and we just killed the lock file.

We only had one major crash and that was due to a full network crash not just a wireless one. It did corrupt the backend but we just replaced it with the previous nights server backup.

Mary

[munkee]

Thank you for the reply Mary. I will just wait and see how things go with the changeover then. I do not know exactly whether we will be switching fully away from being hard wired in but I expect the scenario will end up like yours with partial of both.

I will make sure I keep my backup process running smoothly and see how things go.