Solved

Access - FrontEnd BackEnd Question

Posted on 2014-02-26
6
574 Views
Last Modified: 2014-02-27
Hi,

I have a new database with perhaps 6 or 7 users - fairly lightweight user activity.

I will split it into backend and frontend.

It suits best (for reasons I won't go into) to simple split the database once and NOT on each users PC.   i.e. just one version of the frontend.

QUESTION: Is there benefit in splitting this way OR must I put a front end on each users PC?
0
Comment
Question by:Patrick O'Dea
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 61

Accepted Solution

by:
mbizup earned 100 total points
ID: 39890485
You really should put a front end on each user's computer.  That is accepted as best practice for a multitude of reasons.

- Better performance
- Less prone to corruption
- Allows you to have user-specific tables if temp tables are needed to create reports etc...
- and so on
0
 
LVL 75

Assisted Solution

by:DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform) earned 100 total points
ID: 39890512
If you want to minimize pain, heartache, suffering, depression, anxiety  and a LOT more ... then put a separate copy of the FE on each user's workstation - for the reasons list by mbizup.
Until you do this .... all bets are off when problems start happening ...

mx
0
 
LVL 38

Assisted Solution

by:Jim P.
Jim P. earned 100 total points
ID: 39890598
I'll put a third vote for individual front ends, for all the same reasons.

If you are worried about version issues, there are multiple resolutions.

I have a limited term conversion utility Acc DB's that will be going out of use in a few months. I named the DB App_Convert_Util_V05.mdb. When the DB opens it does a directory search of \\Server\Share\App_Convert_Util_V*.mdb. If it finds a App_Convert_Util_V08.mdb it asks the user if they want the newer version, and then copies it to the user's desktop. The highest version is 62 currently of all the different utilities. Since I figure I'm not going to get to V99 I'm not worried.

In your case it sounds like a long term project and you have a concentrated BE, you can have a Version table in the FE and in the BE have another Version table linked to the FE. On DB open run something to compare the two tables and do a similar thing.

That will take a lot of the angst out of the problem.
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 50

Assisted Solution

by:Gustav Brock
Gustav Brock earned 100 total points
ID: 39891132
You may have your reasons, and it can be possible to run off a single FE file.

However, Access has a habit of writing temporary data into the FE and that may cause troubles. To prevent this, write-protect the physical file (right-click, Properties, mark Read-only). Then temporary data are forced into true temporary files.
This will bring up a warning when a user opens the file. That, however, can be avoided if you open the FE from a shortcut with the /runtime switch, which again may cause other troubles. But check it out.

/gustav
0
 
LVL 9

Assisted Solution

by:Armen Stein - Microsoft Access MVP since 2006
Armen Stein - Microsoft Access MVP since 2006 earned 100 total points
ID: 39892070
If you need more reasons to run the FE locally, here are two:

1. When rolling out a new version, you can't replace the old shared FE until everyone logs out.

As Jim said, a local FE can use fairly simple version checking code to check whether it is current and prompt the user to copy the latest version from the "master" on the server.

2. Related to mbizup's point about user-specific temp tables - sometimes it's handy to have session-specific queries (change the SQL property of a query in code).  These definitely need a local one-user FE.

Cheers,
Armen Stein
0
 

Author Closing Comment

by:Patrick O'Dea
ID: 39892670
Folks,  I think the message is loud and clear!!

It will definitely be a split database !!
0

Featured Post

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Describes a method of obtaining an object variable to an already running instance of Microsoft Access so that it can be controlled via automation.
It’s been over a month into 2017, and there is already a sophisticated Gmail phishing email making it rounds. New techniques and tactics, have given hackers a way to authentically impersonate your contacts.How it Works The attack works by targeti…
In Microsoft Access, learn how to use Dlookup and other domain aggregate functions and one method of specifying a string value within a string. Specify the first argument, which is the expression to be returned: Specify the second argument, which …
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

687 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question