A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

w/ wizard split front end/back end db, how make multiple fronts?



 
 
Thread Tools Display Modes
  #1  
Old August 10th, 2006, 11:30 PM posted to microsoft.public.access.tablesdbdesign
TomsLibrary
external usenet poster
 
Posts: 3
Default w/ wizard split front end/back end db, how make multiple fronts?

I am considering using the Access wizard to split my database into a front
end / back end application. If I decide to do this, the intent would be to
create a way to offer different menus to different types of users (I.e.,
different user groups that have different passwords and logins). If I do
this, I would like to copy the separated front ends to different names, then
edit these front ends (use menus) into different access use patterns for
using the same underlying data table set on the network. Is this a practical
idea? Are there any tips of instructions out there for using this approach?
TomsLibrary
  #2  
Old August 11th, 2006, 04:30 AM posted to microsoft.public.access.tablesdbdesign
Allen Browne
external usenet poster
 
Posts: 11,706
Default w/ wizard split front end/back end db, how make multiple fronts?

To create another front end, just create a blank database, and attach the
tables:
File | Get External | Link

Another front end with very limited functionality makes sense. But if you
want to adapt the menus to the user, then you would need to have all the
objects in the front end, and just expose them differently for different
users. So that would be just one front end file.

Multiple front ends works fine. The only big issue is maintaining them.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"TomsLibrary" wrote in message
...
I am considering using the Access wizard to split my database into a front
end / back end application. If I decide to do this, the intent would be
to
create a way to offer different menus to different types of users (I.e.,
different user groups that have different passwords and logins). If I do
this, I would like to copy the separated front ends to different names,
then
edit these front ends (use menus) into different access use patterns for
using the same underlying data table set on the network. Is this a
practical
idea? Are there any tips of instructions out there for using this
approach?
TomsLibrary



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 08:43 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.