Access 2013 - Linking to multiple database projects

I am asking for advise on the best way to develop and execute a Launchpad approach to the various database projects I am developing.
Looking to have a single database that allows the user to jump to a specific solution based on their current needs.
Correct me if I am wrong, but it seems that keeping all of the details for a specific project in one place would be a better and easier to manage solution that building them all in a single database.

Thanks in advance for your expertise!
Dennis
DGWhittakerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Dennis,

  There's no right or wrong answer in terms of having a single massive DB or a multitude of small ones.

  Depends on app functionality, how much code/logic they might share, security it might require, etc.

  I think most though tend to lean towards a single monolithic app.

Jim.
0
Dale FyeCommented:
I'm not quite sure I understand your question.

Are you talking about something like an application launcher, which keeps track of all of your applications, users, and users assigned to each application?  So that when a user opens the app-launcher, they only see the applications to which they have permissions.  And that when they select a specific application, from those they are authorized to use, it launches that application?
0
DGWhittakerAuthor Commented:
Hi Dale!
Your description would be an ideal solution.
Any advise on bringing that to life?
Thanks!
Dennis
0
Dale FyeCommented:
My application launcher contains three tables: tbl_Applications, tbl_Users, tbl_AppUsers

tbl_Applications contains fields: AppID, AppName, AppVersion, AppPath (where the latest version of the application resides), AppBaseName
AppName is a user friendly version of the application name.  
AppBaseName is what the application will be called on the users computer (without the file extension).

tbl_Users contains fields: UserID, NameF, NameL, ComputerName, BitVersion (32/64)
The reason I have the BitVersion is that when I save the .accde files, I add a bit version to the filename (MyAppName32.accde, MyAppName64.accde) and I use this value associated with the user and the computer they are logged in from to determine which version to use.

tbl_UserApps contains fields:  AppID, UserID

- When the main form loads, it displays the applications associated with the UserId who is logged in.  
- User selects an application and clicks a Launch button.  The code behind the buttons checks:
   1.  to see if the user is on his/her own computer, if so, it checks to see whether the file already exists on the current computer in the users C:\Users\Username\AppData\Roaming\CompanyName\ folder.  If so, it compares the Version# in that file with the version number on the server.  If they match, the code launches application and closes the AppLauncher.
   2.  If the file does not exist, (or the versions don't match) then the code checks to see if the current computer is the computer assigned to this individual.  It does this because the BitVersion of office to use is based on the computer, not the user.  If it is not his/her computer, it looks up the BitVersion for the person with the correct computername.  The code then copies the newest version of the application to the users computer.

There is also a checkbox on the Launch form, something like (chkForceNew) which, if checked, assumes that the version on the users computer is out of date, which allows the user to automatically get the latest version if the version he/she has is corrupted.  It is really a very simple process.

There are additional forms in the Launcher which only an Admin user has access to, to add applications, add users, and assign users to applications.  With this structure.  The only application that the user needs to know about is the AppLauncher, and I generally put that on their desktop, although you could put it in their start menu.  The data for the AppLauncher sits on the organizations server, so that all of the front-ends can get to it.

HTH
Dale
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

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.