In network approach, use Split database or one file with shortcut to every client?

Hi:
Which is better to do , when I need to deploy a small application on a network!
1-      Split my ms app. To front and back end, put the back end in the server and then link all clients to it.
2-      Without splitting the ms app. , just put the app file in the server, and take a shortcut to every client.
Please help
Mohammad Alsolaimanapplication programmerAsked:
Who is Participating?
 
Jeffrey CoachmanMIS LiasonCommented:
0
 
Jeffrey CoachmanMIS LiasonCommented:


In a nutshell:
Split the DB

Front end MDB (accde) on each users workstation.
Linked into one single back end db on a server...
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:

  #1, #1, and #1

Jim.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Any and all cases ... Split, each user separate copy of FE. Period.

mx
0
 
Jeffrey CoachmanMIS LiasonCommented:
...
I guess you asked this question for a reason...

I am sure Jim and MX can give you the more "Ethereal" explanations...

As always, you can run the db any way you want, dealing with the fallout is another issue...
;-)

Did you read the links I posted?

Sure, if you have only one user, on one machine, the single shortcut will work, ...kinda, ...for a while perhaps...
But even I would not do that.
At least with a split db (FE, mde) you can update the FE without disturbing the user(s) and the db has some basic protections, ...etc

The big issue with me a single db is that as soon as you have more than one user, if User A crashes the DB, the entire DB is dead.
With a FE/BE, the user might crash "their" FE, but this commonly leaves the BE unscathed

Besides, on a very basic, non technical level, it is simply good practice to split the db.
This helps you to identify issue with the links themselves, the way you reference the links, permissions to the target DB on the server, network connection issues, database performance (when to link to a table and when to make a table local/static), file naming, ...etc

Because of the way Access is set up to run, a single db run from a shortcut will have to pull the *entire* database over the wire.
So even with a single user, splitting the db is a good idea, if only to reduce network traffic.

Remember, the BE is on the server for some very good reasons.
The server should be accessible to all the users
The server is a "Super" machine, equipped with all manner of beefy hardware, RAIDS, backup software, power backup systems, ..etc


Again, I am sure Jim and MX can give you the more "Ethereal" explanations...
(Security concerns, Access' internal inner workings, ...etc)

;-)

Jeff


0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:

I should note that all professional Access applications have the split configuration, for the following reasons

1) Possibly eliminate a problem you may be having.

2) Development on your FE can continue w/o affect live data in the back end.   A major reason to do so.

3) Testing FE changes will not affect the live data, since you can use a copy of the data BE

4) Spitting makes it much easier to plan for migration to a server database such as SQL Server, etc.

5) A split configuration allows you to create an MDE FE wherein your forms, reports and modules are secure.

6) Backing up and protecting data in the BE is *much* easier with a split configuration.

7) Users in the FE will not be able to change table designs, etc.

Again, all professional Access databases use a split configuration ... as I have for 19+ years.

After you split the db, you put a copy of the FE on each workstation - each linked to the common BE.  This will greatly help minimize many of the issues we see frequently here on EE.

Additional (must read) references on the subject:
      
Splitting Microsoft Access Databases to Improve Performance and Simplify Maintainability
http://www.fmsinc.com/MicrosoftAccess/DatabaseSplitter/Index.html

Split your Access database into data and application
http://allenbrowne.com/ser-01.html

How to manually split a Access database in Microsoft Access
http://support.microsoft.com/?kbid=304932

mx
0
 
Jeffrey CoachmanMIS LiasonCommented:
#4, great point
0
 
Jeffrey CoachmanMIS LiasonCommented:
trailer...

Access db size limit is 2GB, so with one db, this is your hard limit.
With a very basic split db, you at least then have 4GB
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Well, still only 2GB in any one back end ....but, that can be all data ...

mx
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:

 plus you can put one table in each DB if needed, so really your limit is a single table of 2GB.  But doing so precludes the use of relationships (you can't enforce relationships across containers).

Jim.
0
 
Armen Stein - Microsoft Access MVP since 2006PresidentCommented:
Split!

And then use our free J Street Access Relinker at www.JStreetTech.com/downloads.

Cheers,
Armen
0
 
Mohammad Alsolaimanapplication programmerAuthor Commented:
thank you very much for participate
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.