I have a user-level secure database that I've split. However, while users must log into the Front-End, the Back-end can be opened without logging in.
I then used the security wizard to protect the B/E using the same workgroup, which seems to work as far as protecting the B/E from being opened without logging in.
However, when a user logs into the front-end now, a link tables message is shown, and the user cannot perform this function. Permissions are identical on both the F/E and B/E, and each can be opened separately. The only person that can link is an administrator. And even though the tables were linked by an Administrator, a different user logging into the same F/E is asked to link, and cannot do so.
In short, is there a way I can use a split database in a multiuser environment where both the F/E and B/E are secure?
I then used the security wizard to protect the B/E using the same workgroup, which seems to work as far as protecting the B/E from being opened without logging in.
However, when a user logs into the front-end now, a link tables message is shown, and the user cannot perform this function. Permissions are identical on both the F/E and B/E, and each can be opened separately. The only person that can link is an administrator. And even though the tables were linked by an Administrator, a different user logging into the same F/E is asked to link, and cannot do so.
In short, is there a way I can use a split database in a multiuser environment where both the F/E and B/E are secure?