If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
networking
What is the problem with wireless networking Access, we have this but only
internal |
#2
|
|||
|
|||
networking
Hi Steve,
Wireless access to a JET database is generally discouraged because this type of network connection is subject to dropping out, as one moves about the area. The number one cause of JET database corruption is interrupted write operations. Here are two sites that provide lots of good information on the topic of corruption: Preventing Corruption (Allen Browne) http://allenbrowne.com/ser-25.html Corrupt Microsoft Access MDBs FAQ (Tony Toews) http://www.granite.ab.ca/access/corruptmdbs.htm You copy of Access operates directly on the file in a shared folder on a server. We call this "File Server", as opposed to true "Client Server". So, if the communication is mangled by the time it reaches your .mdb file, due to dropped packets on a flakey network, you can easily end up with a corrupted file. A true Client Server database product, such as SQL Server or Oracle, acts as an intermediary between you and the database. If the server does not understand the communication, it's not going to turn around and hose the data in the database. You have no such protection with direct file access. Tom Wickerath Microsoft Access MVP http://www.accessmvp.com/TWickerath/ http://www.access.qbuilt.com/html/ex...tributors.html __________________________________________ "stevecz" wrote: What is the problem with wireless networking Access, we have this but only internal |
Thread Tools | |
Display Modes | |
|
|