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. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
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
|
|||
|
|||
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 | |
|
|