Importing

[Ann]

I secured a split 2002 Access database giving myself Admin rights and nobody
else. Both the fe and be were secured using the wizard and creating a new
..mdw file. I didn't have any problems and have done this multiple times to
make sure I am understanding everything correctly. I did many tests on both
the fe and be to see if I can get into them but can't. Until I tried to
create a new database using the default system.mdw file that was never
altered and import the information. I couldn't import any information from
the fe database but all of the tables in the be were imported into a new
database allowing me or anyone else access to all of the data. Does Access
work this way or could I have made a mistake when I secured the be database?
Thanks for the help.

 

[Joan Wild]

You made a mistake when you secured the be.

You should both mdb files using the same mdw file.

Just open the fe and login (this'll make sure you've started a session with the secure mdw). Then open the be and run the wizard (or you could just secure it manually).

--
Joan Wild
Microsoft Access MVP
:I secured a split 2002 Access database giving myself Admin rights and nobody
: else. Both the fe and be were secured using the wizard and creating a new
: .mdw file. I didn't have any problems and have done this multiple times to
: make sure I am understanding everything correctly. I did many tests on both
: the fe and be to see if I can get into them but can't. Until I tried to
: create a new database using the default system.mdw file that was never
: altered and import the information. I couldn't import any information from
: the fe database but all of the tables in the be were imported into a new
: database allowing me or anyone else access to all of the data. Does Access
: work this way or could I have made a mistake when I secured the be database?
: Thanks for the help.

 

[Ann]

I don't know what I'm doing wrong. I tried it again and got the same result.
Then I started with a new database and went through splitting, securing the
fe then the be again and still get the same result. The be is using the
correct .mdw file because prior to adding security I could open it without a
password. Afterwards I need the password. The workgroup to be used is part
of the shortcut so I tried to open both the fe and be without using the
shortcut. The fe still won't let me open it up but the be will. The only
time it uses the correct workgroup is when I use the shortcut.

After securing the fe here is what I did. Opened the fe then opened the be.
Started the wizard. Made sure I ws modifying the current workgroup.
Verified all objects were selected, checked the groups I had used in the fe.
After that I just clicked Next on everything to keep the same users and
permissions. I'm using an ElementK, Level 4 manual. I can reuse the files
so I'm going to try again.

 

[Joan Wild]

Why don't you try securing the single mdb, and then split it.

Do the splitting manually as the splitter wizard will do it wrong. See
www.jmwild.com\splitsecure.htm


--
Joan Wild
Microsoft Access MVP
:I don't know what I'm doing wrong. I tried it again and got the same result.
: Then I started with a new database and went through splitting, securing the
: fe then the be again and still get the same result. The be is using the
: correct .mdw file because prior to adding security I could open it without a
: password. Afterwards I need the password. The workgroup to be used is part
: of the shortcut so I tried to open both the fe and be without using the
: shortcut. The fe still won't let me open it up but the be will. The only
: time it uses the correct workgroup is when I use the shortcut.
:
: After securing the fe here is what I did. Opened the fe then opened the be.
: Started the wizard. Made sure I ws modifying the current workgroup.
: Verified all objects were selected, checked the groups I had used in the fe.
: After that I just clicked Next on everything to keep the same users and
: permissions. I'm using an ElementK, Level 4 manual. I can reuse the files
: so I'm going to try again.
:
: "Ann" wrote:
:
: > I secured a split 2002 Access database giving myself Admin rights and nobody
: > else. Both the fe and be were secured using the wizard and creating a new
: > .mdw file. I didn't have any problems and have done this multiple times to
: > make sure I am understanding everything correctly. I did many tests on both
: > the fe and be to see if I can get into them but can't. Until I tried to
: > create a new database using the default system.mdw file that was never
: > altered and import the information. I couldn't import any information from
: > the fe database but all of the tables in the be were imported into a new
: > database allowing me or anyone else access to all of the data. Does Access
: > work this way or could I have made a mistake when I secured the be database?
: > Thanks for the help.

 

[Ann]

That worked!!! Thanks so much!!! I had to laugh though. I spent the last
three hours researching and trying different things. Including splitting it
myself but I was doing it first. Nothing I tried worked until this. This
site and the people who help are the best!