T
TomsLibrary
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
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