Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / January 2008

Tip: Looking for answers? Try searching our database.

LAN or WAN

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
scott04 - 23 Nov 2007 14:21 GMT
I ususally design most of my databases for my local office and place it on a
network shared using a FE and BE setup.  My corporate office is wanting to
have me create a database that can be used for our office, an office in the
midwest, and an office on the west coast.  There is a corporate share drive
that can be accessed by all three centers.  My main question is can i design
it the same way and place the BE on the share and FE on each ones C drive?  I
have read articles on WAN connections and currently am not sure if this is a
WAN network.  Any thoughts?  Thanks.
Albert D. Kallal - 23 Nov 2007 15:23 GMT
I give thoughts, and solutions here:

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

Albert D. Kallal    (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

Tony Toews [MVP] - 24 Nov 2007 04:51 GMT
>I ususally design most of my databases for my local office and place it on a
>network shared using a FE and BE setup.  My corporate office is wanting to
[quoted text clipped - 4 lines]
>have read articles on WAN connections and currently am not sure if this is a
>WAN network.  

Yes, that is a WAN network.  Unless there is 100 mpbs connection
between those offices you could be in for lots of troubles including
very slow response time and risk of corruption.  

Note that there was a posting from a very credible individual who
stated that he had a client with offices scattered through out a state
which were on a 100 mpbs connection.  And Access worked well in that
environment.

Tony
Signature

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/

David W. Fenton - 25 Nov 2007 01:05 GMT
> I ususally design most of my databases for my local office and
> place it on a network shared using a FE and BE setup.  My
[quoted text clipped - 5 lines]
> C drive?  I have read articles on WAN connections and currently am
> not sure if this is a WAN network.  Any thoughts?

Windows Terminal Server.

Signature

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

ThomCarr - 26 Nov 2007 06:03 GMT
On Nov 24, 8:05 pm, "David W. Fenton" <XXXuse...@dfenton.com.invalid>
wrote:
> =?Utf-8?B?c2NvdHQwNA==?= <scot...@discussions.microsoft.com> wrote
> innews:1E978B2B-465D-48DF-9F56-72E422935DB5@microsoft.com:
[quoted text clipped - 14 lines]
> David W. Fenton                  http://www.dfenton.com/
> usenet at dfenton dot com    http://www.dfenton.com/DFA/

Yes, Windows Terminal Server is the answer.  I currently using it in
Windows 2003 SBS environment for remote users. It is a single plaform
that I can manage remotly on an very high speed backbone (1GB) from
the SBS Server.

For a Access FE can be copied and "assigned" to each user profile as
they login very quickly. (the master production copy of the FE would
be on one of TS server volumes so there is little or no network
traffic when copied.)  The BE would be in a secure subfolder of the
"comany folder" of the SBS server (or an other server in the center
office).

Better yet, Windows Server 2008 Terminal Services.

It "enable[s] remote access for existing "WAN-unfriendly"
applications" that can be "integrate with the user's local desktop".

Older versions presented the user with a full remote desktop and
profile [which can be confusing for some], with this version user can
be limited to only the application dialog "windows".  Citrix
presentation server had these features also.

An other major advantage of this approach is Access does not need to
be deployed to all of the users desktops.  You only need the licenses
for Terminal Services and Office Pro on the TS server.

Thom Carr
ThomCarr - 26 Nov 2007 06:07 GMT
> On Nov 24, 8:05 pm, "David W. Fenton" <XXXuse...@dfenton.com.invalid>
> wrote:
[quoted text clipped - 47 lines]
>
> - Show quoted text -

Forgot the link to Windows Server 2008 Terminal Services

http://www.microsoft.com/windowsserver2008/terminal-services/default.mspx
david - 07 Jan 2008 22:30 GMT
The runtime for A2007 is free now, so for free you can install
the Access runtime (you still need the TS licences).

Multiple licences for full (retail) Access/Office Pro are still required.

I haven't looked for a long time, but it used to be that you had a choice
of per-person licences (One person, any desk), or per desk licence
(One desk, any person).

If you have 3 people using full (retail) Access at the same time, even
on Terminal  Services, you need 3 Access/Office Pro licences.

(david)

> On Nov 24, 8:05 pm, "David W. Fenton" <XXXuse...@dfenton.com.invalid>
> wrote:
[quoted text clipped - 44 lines]
>
> Thom Carr
David W. Fenton - 12 Jan 2008 23:24 GMT
> The runtime for A2007 is free now, so for free you can install
> the Access runtime (you still need the TS licences).

But that's still much more complicated than administering Terminal
Server. And it doesn't help in a WAN situation at all.

Signature

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

david - 15 Jan 2008 00:29 GMT
>> The runtime for A2007 is free now, so for free you can install
>> the Access runtime (you still need the TS licences).
>
> But that's still much more complicated than administering Terminal
> Server. And it doesn't help in a WAN situation at all.

You need MS Office licences if you use Terminal Server. You can
use a full 'retail' MS Office Pro licence for each user on your Terminal
Server, or you can use a 'runtime' MS Access licence for each user on
your Terminal Server.

You only need one licence per user. If the user has a desktop MS Office
Pro licence, that is sufficent.  If the user does not have an Office Pro
licence, a MS Access Runtime Licence can be used.

In addition to an Office/Access licence for each user, you need
a Terminal Server Client licence for each user.

(david)
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.