Unless they need to know what the other nurses have updated, I think you'd
be best off using replication. Once they're back to their desk, they can
hook up to the LAN and update the master database.

Wireless connectivity from the mobile workstations actually running
Access MDB/MDE's to a file server is strongly not recommended.

However if the mobile workstations are connecting to Citrix servers
via wireless then that's just fine.  We recommend folk who need to use
wireless to user either Terminal Server/Citrix or SQL Server.

<digression>This assumes, of course, that the Terminal Server/Citrix
servers aren't in turn using wireless to connect to the file server.
However that is exceedingly unlikely.  <smile>  And any IT folks which
do so should really consider a career in, ummm, hmm I was going to
suggest a very large corporate hog farm but that would be unfair to
the hogs.

(I have relatives who run hog farms.  As a teenager I spent two
summers feeding hogs and cleaning hog barns with a snow shovel and
wheel barrow.) </digression>

Tony

If your using citrix....then  you much home free. Even a total break in the
connection, or hitting the re-set button on your client computer will NOT
hurt this.

In fact, if you accidentally pull the plug on the client computer...you
simply re-boot..and launch the remote desktop...you be resumed exactly were
you left off..

your use of citrix is ideal...and especially when you using wireless...

Access never makes the trip down the wire...and thus your safe....

If they are running it via Citrix Terminal Server, then there's no
issue. The issue with Access and wireless is with an Access front
end connected across a wireless connection to a Jet back end. If the
back end is SQL Server or some other server database, it's not an
issue. And if you're not connecting across the wire (as you are not
with a remote session running on Windows Terminal Server or Citrix),
then it's also not an issue.

What website? You're using a website that republishes public Usenet
groups that are available without using that website at all. I'm not
pleased that sites like Access Monster are repackaging Usenet
content as though it's their own -- it's misleading, in my opinion,
and borderline copyright violation.

you can't use Wireless with Access databases

you'd be better off moving to Access Data Projects and SQL Server

It just amazes me -- if your database is too much of a wimp to support
wireless then you need a skills upgrade