database split before or after security?

Hi Access Heros,
I created a new database in Access 2003. I created a new workgroup file as
owner. As owner, I created a new database and imported tables from original
db for my backend. Then I created another database, as workgroup owner and
imported queries, forms and reports, as frontend. Does it make sense to do
it this way? Doesn't this set security on both the backend and frontend?

I guess I am asking this question because when reading other threads, people
ask whether to set security on backend or frontend. This confuses me. Isn't
security on both?

Thank you
Charlie

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200603/1
.

Relevant Pages

  • Re: Where to place the workgroup file
    ... I have a homegrown security that I use on my back-end files. ... only I (the Owner) can get in to the back-end files. ... application to use a database password. ... database and the workgroup file can leave the building on that laptop. ...
    (microsoft.public.access.security)
  • RE: no permissions for any users
    ... This means that you used the wrong workgroup file to open this database ... and it means that you did not properly secure the database (since you ... you log in as will be the owner of all these imported objects. ...
    (microsoft.public.access.security)
  • Re: OMG! Need help w/security issue
    ... Those items owner cannot be changed at all, ... >> I have an Access '97 database using a workgroup file. ... >in use when the mdb was created. ...
    (microsoft.public.access.conversion)
  • Re: OMG! Need help w/security issue
    ... > I have an Access '97 database using a workgroup file. ... But you say below that you can't change the owner of the database, ... the owner of the DATABASE object ...
    (microsoft.public.access.conversion)
  • Re: Sorting out security
    ... > MS Access security. ... > created a new workgroup, added a password for the Admin role, added ... > remote logins to a secured database. ... The location of the current workgroup file is recorded in the ...
    (microsoft.public.access.security)
Loading