Problematic access

%3CLINGO-SUB%20id%3D%22lingo-sub-1547838%22%20slang%3D%22en-US%22%3EProblematic%20access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1547838%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EIs%20it%20possible%20to%20have%20multiple%20user%20accesses%20on%20the%20access%20platform%3F%20if%20yes%2C%20what%20would%20be%20the%20solution%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1547838%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1547958%22%20slang%3D%22en-US%22%3ERe%3A%20Problematic%20access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1547958%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F741045%22%20target%3D%22_blank%22%3E%40Nicola%20_%20Borzacchiello%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20Access%20is%20designed%20to%20support%20multiple%20users.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELike%20all%20fully%20developed%20relational%20database%20applications%20would%20be%2C%20you%20need%20to%20design%20it%20with%20three%20components%2C%20or%20layers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EData%20Layer%3A%20This%20is%20the%20component%20of%20the%20application%20holding%20the%20data.%20Data%20is%20stored%20in%20Tables.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInterface%20Layer%3A%20This%20is%20the%20component%20of%20the%20application%20with%20the%20objects%20through%20which%20users%20interact%20with%20that%20data.%20Forms%20and%20Reports%20are%20the%20interface%20objects%20in%20your%20solution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELogic%20Layer%3A%20This%20is%20the%20code%20by%20which%20you%20automate%20processes.%20In%20Access%2C%20this%20can%20be%20either%20macros%20or%20VBA%2C%20or%20both.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20MS%20Access%20application%20contains%20all%20of%20the%20necessary%20tools%20for%20creating%20tables%20and%20queries%2C%20for%20creating%20forms%20and%20reports%2C%20and%20for%20writing%20VBA.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnlike%20other%20solutions%2C%20though%2C%20an%20accdb%20is%20a%20unitary%20file%2C%20which%20contains%20all%20of%20those%20components%20by%20default.%20In%20order%20to%20prepare%20it%20for%20deployment%20to%20a%20GROUP%20of%20users%2C%20therefore%2C%20you%20must%20separate%20the%20data%20layer%2C%20i.e.%20the%20tables%2C%20from%20the%20other%20components.%20And%20you%20do%20that%20by%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Foffice%2Fsplit-an-access-database-3015ad18-a3a1-4e9c-a7f3-51b1d73498cc%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Esplitting%20the%20accdb%3C%2FA%3E%20into%20two%20accdbs.%20One%2C%20usually%20referred%20to%20as%20the%20Front%20End%2C%20contains%20ONLY%20the%20interface%20and%20logic%20components.%20The%20other%2C%20usually%20referred%20to%20as%20the%20Back%20End%2C%20contains%20ONLY%20the%20tables%20for%20the%20data%20storage.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlace%20the%20Back%20End%20in%20a%20shared%20folder%20to%20which%20all%20users%20have%20permissions.%20They%20will%20all%20work%20with%20that%20copy%20of%20the%20accdb%20because%20they%20must%20share%20that%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPut%20an%20individual%20copy%20of%20the%20Front%20End%20on%20each%20user's%20computer.%20This%20is%20their%20personal%20copy%20of%20the%20interface%20and%20code%2C%20linked%20to%20the%20shared%20data%20in%20the%20Back%20End.%20Do%20NOT%2C%20under%20any%20circumstances%2C%20let%20users%20share%20a%20Front%20End.%20Corruption%20is%20highly%20likely%20in%20such%20scenarios.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%20many%20other%20possible%20considerations%2C%20of%20course%2C%20such%20as%20deployment%20methods%20and%20even%20IT%20support.%20Invest%20some%20time%20in%20a%20search%20on%20topics%20relating%20to%20%22Splitting%20your%20accdb.%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1547967%22%20slang%3D%22en-US%22%3ERe%3A%20Problematic%20access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1547967%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20of%20course%2C%20but%20you%20need%20to%20split%20your%20database%20and%20deploy%20a%20copy%20of%20the%20front-end%20to%20each%20user%20and%20this%20must%20be%20over%20a%20wired%20LAN%20(anything%20else%20you%20are%20asking%20for%20trouble%20and%20data%20corruption).%26nbsp%3B%20You%20can%20learn%20more%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.devhut.net%2F2017%2F04%2F09%2Fsetting-up-an-ms-access-database%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.devhut.net%2F2017%2F04%2F09%2Fsetting-up-an-ms-access-database%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.devhut.net%2F2017%2F04%2F20%2Faccess-best-practices-and-troubleshooting-steps%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.devhut.net%2F2017%2F04%2F20%2Faccess-best-practices-and-troubleshooting-steps%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1548178%22%20slang%3D%22en-US%22%3ERe%3A%20Problematic%20access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1548178%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126074%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Eby%20changing%20the%20beck%20file%2C%20does%20the%20frone%20file%20change%20automatically%2C%20and%20the%20opposite%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1552875%22%20slang%3D%22en-US%22%3ERe%3A%20Problematic%20access%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1552875%22%20slang%3D%22en-US%22%3EChange%20in%20what%20way.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20are%20in%20the%20database%2C%20using%20the%20front-end%20and%20edit%20records%2C%20the%20data%20is%20being%20updated%20in%20the%20backend.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20edit%20data%20directly%20in%20the%20backend%2C%20which%20no%20one%20should%20ever%20be%20doing%2C%20everyone%20in%20the%20front-end%20would%20see%20the%20changes.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Is it possible to have multiple user accesses on the access platform? if yes, what would be the solution?

4 Replies
Highlighted

@Nicola _ Borzacchiello 

 

Yes, Access is designed to support multiple users. 

 

Like all fully developed relational database applications would be, you need to design it with three components, or layers.

 

Data Layer: This is the component of the application holding the data. Data is stored in Tables. 

 

Interface Layer: This is the component of the application with the objects through which users interact with that data. Forms and Reports are the interface objects in your solution.

 

Logic Layer: This is the code by which you automate processes. In Access, this can be either macros or VBA, or both.

 

The MS Access application contains all of the necessary tools for creating tables and queries, for creating forms and reports, and for writing VBA.

 

Unlike other solutions, though, an accdb is a unitary file, which contains all of those components by default. In order to prepare it for deployment to a GROUP of users, therefore, you must separate the data layer, i.e. the tables, from the other components. And you do that by splitting the accdb into two accdbs. One, usually referred to as the Front End, contains ONLY the interface and logic components. The other, usually referred to as the Back End, contains ONLY the tables for the data storage.

 

Place the Back End in a shared folder to which all users have permissions. They will all work with that copy of the accdb because they must share that data.

 

Put an individual copy of the Front End on each user's computer. This is their personal copy of the interface and code, linked to the shared data in the Back End. Do NOT, under any circumstances, let users share a Front End. Corruption is highly likely in such scenarios.

 

There are many other possible considerations, of course, such as deployment methods and even IT support. Invest some time in a search on topics relating to "Splitting your accdb."

Highlighted

Yes, of course, but you need to split your database and deploy a copy of the front-end to each user and this must be over a wired LAN (anything else you are asking for trouble and data corruption).  You can learn more

 

https://www.devhut.net/2017/04/09/setting-up-an-ms-access-database/

https://www.devhut.net/2017/04/20/access-best-practices-and-troubleshooting-steps/

 

Highlighted

@George Hepworth 

 

by changing the beck file, does the frone file change automatically, and the opposite?

Highlighted
Change in what way.

If you are in the database, using the front-end and edit records, the data is being updated in the backend.

If you edit data directly in the backend, which no one should ever be doing, everyone in the front-end would see the changes.