Albert D Kallal

[simcon]

In the article below Albert states that it is highly risky running an Access
system where the front end and back end are on different computers on the
network and the 'client' compters are using wireless networking.
I would be interested to know if anyone is using this configuration with
regard to wireless clients without problem.

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

 

[boblarson]

I would find it very unlikely that someone is using it without any problems.
It is very risky, especially since Access is very fragile when it comes to
network connections. Any network disconnection, no matter how brief, can
cause irrecoverable corruption. Wireless networks are not as stable as wired
networks, as far as disruptions are concerned, so it is a much greater risk
to use wireless connections with Access databases.

--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
If my post was helpful to you, please rate the post.
__________________________________

 

[Albert D. Kallal]

I do think the little graphic in that article with the bits and pieces of
the file in the memory in the computer, and the other bits and pieces on the
disk drive does is a goo illustration as to why the situation can be
unreliable.

I have tested and used ms-ccess on a wireless network at home. It does work
quite well, but as others mentioned there is this issue of breakage of the
network connection, and I really don't think it's reliable enough for
production environment.

If you're going to use a wireless network, then I would suggest you want use
one of several of Microsoft's free SQL servers products, as they make a
rather decent back end for your MS application anyway. That way when you
suffer minor a temporary disconnects in the network, you'll only lose some
data, but not actually damage the actual data file itself.

Of course I suggest other ideas like using true thin client technology, but
simply using a free SQL server for the backend does work quite well in this
case, and these database servers are relatively free in terms of software
costs now.....

 

[simcon]

Thank you Albert I think we have already come round to your way of thinking
and have decided to use MS SQL Server Express 2005 as the 'back end'. No
doubt we will incur an additional learning curve but hopefully this will
result in a far more reliable system than using native Jet.

 

[Tony Toews [MVP]]

I have tested and used ms-ccess on a wireless network at home. It does work
quite well, but as others mentioned there is this issue of breakage of the
network connection, and I really don't think it's reliable enough for
production environment.

In a home environment you may not notice problems as you may be
physically close enough to the Wireless Access Point that you will
always get a good signal.

However as you get on to the fringes of the signal then things get
much more "interesting".

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/