Networking Access

  • Thread starter Thread starter tpitman
  • Start date Start date
T

tpitman

I have a shared MS Access application on Win NT. I have used the
database splitter to split the forms & tables, which are held on the
same PC.
The network users access both over the network.
My problem is that when closing down the Server PC, a message is
generated on the screen, informing the user of others using the
application over the network, although they have previously closed
down.
Can anyone help please ?
 
Arvin,

What about using a front end / back end on the server and connecting network
workstations via terminal services? What are the pros and cons to this
approach?

--

Richard Overturf
Harvest Data Systems
New Port Richey, FL USA
(e-mail address removed)
 
That is quite workable, but each user should still have his/her own copy of
the front end.

In general, unless you are working over the Internet or a very slow WAN,
though, you may not get much advantage over a split-Access-Jet arrangement.
That is, if you have a properly designed multiuser system.

Multiple users in the same front end drastically increases the probability
of corruption.

Best collection of detailed information and links I know of in re: Access
multiuser performance and avoiding corruption is at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm. There's an introductory presentation
I did on multiuser at http://appdevissues.tripod.com/downloads.htm that
might be worth a look.

Larry Linson
Microsoft Access MVP
 
Terminal Services only requires a single copy of the database, but it should
still be a split application running on the server. Keep in mind that a
split application allows upgrading the front-end application with little or
no affect on the data. Changes to the back-end (data) may still be
necessary, but there is less overall disruption of work-flow.

The real advantage to running Terminal Server is use on a Wide Area Network
with a limited number of users. Over a WAN, there is almost no corruption
issues due to hardware (NIC) problems because Terminal Servers do not send
data of the wire, they send an image of an instance of the application,
running on the server.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
How many concurrent users can be on an Access front end/back end via
Terminal Services? What are the drawbacks to using TS instead of moving to
a client server approach?

Thanks
 
R. Overturf said:
How many concurrent users can be on an Access front end/back end via
Terminal Services? What are the drawbacks to using TS instead of moving to
a client server approach?
Click to expand...

Other than removing the network from the equation there is no difference to
running Access over TS than doing it without TS. Of course that assumes that
the Front End and Back End file both reside on the TS drives and not elsewhere
on the network.

The advantages (and disadvantages) of moving to a true server-based Back End are
also not affected by the use of TS. In other words, if you need the
concurrency, scalability, and security of a server-based Back End then TS will
not satisfy those requirements.
 
Rick Brandt said:
Other than removing the network from the equation there is no difference to
running Access over TS than doing it without TS. Of course that assumes that
the Front End and Back End file both reside on the TS drives and not elsewhere
on the network.
Click to expand...

Actually with only one TS and both the FE and BE on the same computer
you might be able to run a heckuva lot of users on that. No network
overhead.

However I don't know how many IT depts would like to have such a
setup.
The advantages (and disadvantages) of moving to a true server-based Back End are
also not affected by the use of TS. In other words, if you need the
concurrency, scalability, and security of a server-based Back End then TS will
not satisfy those requirements.
Click to expand...

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
 
Arvin Meyer said:
Terminal Services only requires a single copy of the database, but it should
still be a split application running on the server. Keep in mind that a
split application allows upgrading the front-end application with little or
no affect on the data. Changes to the back-end (data) may still be
necessary, but there is less overall disruption of work-flow.

The real advantage to running Terminal Server is use on a Wide Area Network
with a limited number of users. Over a WAN, there is almost no corruption
issues due to hardware (NIC) problems because Terminal Servers do not send
data of the wire, they send an image of an instance of the application,
running on the server.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
Click to expand...
 
Back
Top