Access updates over small wireless lan?????

[Bob Alston]

I just acquired a pro bono nonprofit client who has various problems
with Access that they want me to address. In our initial discussion,
they mentioned that their network is a LInksys wireless network,
connecting 5 PCs in a small access. Of course, my ears perked up at the
mention of Access and wireless network in the same sentence.

I have always read that Access is subject to corruption over anything
but the most robust LAN.

Realistically, what do you think is the likelihood of corruption
problems in linking FE to BE over a wireless network?

Bob

[lyle fairfield]

On Apr 25, 11:21*am, Bob Alston <[e-mail]:

I just acquired a pro bono nonprofit client who has various problems
with Access that they want me to address. *In our initial discussion,
they mentioned that their network is a LInksys wireless network,
connecting 5 PCs in a small access. *Of course, my ears perked up at the
mention of Access and wireless network in the same sentence.

I have always read that Access is subject to corruption over anything
but the most robust LAN.

Realistically, what do you think is the likelihood of corruption
problems in linking FE to BE over a wireless network?

Bob

I've done this minimally without problems.
If I had to do it extensively I'd:

[lyle fairfield]

On Apr 25, 11:33*am, lyle fairfield <[e-mail]:

On Apr 25, 11:21*am, Bob Alston <[e-mail]:

I just acquired a pro bono nonprofit client who has various problems
with Access that they want me to address. *In our initial discussion,
they mentioned that their network is a LInksys wireless network,
connecting 5 PCs in a small access. *Of course, my ears perked up at the
mention of Access and wireless network in the same sentence.

I have always read that Access is subject to corruption over anything
but the most robust LAN.

Realistically, what do you think is the likelihood of corruption
problems in linking FE to BE over a wireless network?

Bob

I've done this minimally without problems.
If I had to do it extensively I'd:

not use Google Groups on Opera today as the combination seems to be
corrupted! :-)

and

use SQLExpress as a backend;
use Wireless N ... I have reports that this is indistinguishable from
a a wire;

[Larry Linson]

I haven't, personally, networked a multiuser database application over
wireless but have heard many report that wireless networking seems to have
improved to the point that it can (sometimes?) be used instead of a wired
network. I'd be likely to "overdo" the backup until I was convinced that it
is stable.

Most problems/corruptions caused by a dropped connections can be handled
with compact and repair. But, not all can, so it's just a matter of
weighing the risk against the cost of avoidance.

Good luck, Bob, and let us know how it works out!

Larry Linson
Microsoft Office Access MVP
"Bob Alston" <bo********@yahoo.comwrote in message
news:eF************@newsfe06.lga...

>I just acquired a pro bono nonprofit client who has various problems with
Access that they want me to address. In our initial discussion, they
mentioned that their network is a LInksys wireless network, connecting 5
PCs in a small access. Of course, my ears perked up at the mention of
Access and wireless network in the same sentence.

I have always read that Access is subject to corruption over anything but
the most robust LAN.

Realistically, what do you think is the likelihood of corruption problems
in linking FE to BE over a wireless network?

Bob

[David W. Fenton]

"Larry Linson" <bo*****@localhost.notwrote in
news:dqrQj.46$E77.39@trnddc05:

Most problems/corruptions caused by a dropped connections can be
handled with compact and repair. But, not all can, so it's just a
matter of weighing the risk against the cost of avoidance.

I would never do it. Wireless networks can come in and out all the
time. Secondly, you're sharing the radio spectrum with every other
WiFi network within range, and thus things that someone else is
doing on their network can affect the bandwidth available to you on
yours.

It's a terrible idea -- never use Access on a wireless network if
the back end is Jet.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[lyle fairfield]

On Apr 25, 7:31*pm, "David W. Fenton" <[e-mail]>
wrote:

"Larry Linson" <[e-mail] innews:dqrQj.46$E77.39@trnddc05:

Most problems/corruptions caused by a dropped connections can be
handled with compact and repair. *But, not all can, so it's just a
matter of weighing the risk against the cost of avoidance.

I would never do it. Wireless networks can come in and out all the
time. Secondly, you're sharing the radio spectrum with every other
WiFi network within range, and thus things that someone else is
doing on their network can affect the bandwidth available to you on
yours.

I had forgotten about that. I've seen very bad problems with wireless
networks and wireless phones in the same area. When the phone rings,
the network disconnects. Sometimes this can be helped by changing
channels but that doesn't seem to work all the time.

[Tony Toews [MVP]]

Bob Alston <bo********@yahoo.comwrote:

>Realistically, what do you think is the likelihood of corruption
problems in linking FE to BE over a wireless network?

The likelihood of corruption is significantly higher with a wireless network.

And I disagree with Lyle on the wireless N networks. They will still suffer from the
fundamental problems of wireless even if they are 10x better than the older wireless
networks. There is still too much of a risk of corruption.

As David states go with SQL Server then.

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/

[lyle fairfield]

Wilf Carter confessed to me that the original title of this song was
"Friday Nights on the Alberta Range"

Hang the key on the bunkhouse door ‘cause we’ll be late to-night
Don’t leave the light a-burnin’ dear, we may not look right
The trail is long, the goin’s tough and someone may get tight
So hang the key on the bunkhouse door ‘cause we’ll be late to-night

On Apr 26, 12:51*am, "Tony Toews [MVP]" <[e-mail]>
wrote:

As David states go with SQL Server then.

[The Frog]

I have tried many times to create stable Access BE / FE with wireless
networks, and even with 100% signal strengrh and uninterrupted
bandwidth, there are still problems.

Go with SQL Server for this one, and use transactions. I really dont
know why the corruption occurs with Access, only that it does.

Cheers

The Frog