Security nightmare - 2 mdw's mixed up

[Rob]

Hi, some things that worked for me. The shortcut probably refers to the mdw
file as a switch (/). The workgroup file that is applicable to the database
is therefore loaded when the db is opened. You must however have used or
specified the mdw file during creation. Once Access is passed the mdw file to
use it keeps on using the that one until u specify another one to use
(security settings). If no mdw was specified for the db it uses the default
"blank" privileges that is loaded with Access. If you replace this mdw with
your own then you can not access that db. Solution: copy the "blank" mdw from
another machine and use that for the db. Also delete the mdw switch from the
shortcut target for the db that is not supposed to use the mdw.

Hope this helps.

 

[Rob]

Hi, the reason is that your collegue is not using the same mdw (workgroup)
file as you although you are working on a shared drive. Solution: (1) use a
shortcut with the workgroup switch (/) included in the target; (2) specifiy
the workgroup file to use at your collegue's workstation (subscribe to it) -
this means that the mdw must be available on the network drive (preferably
where the db is located; (3) use th packaging wizard available with Office
Developer to distribute your db as a setup package. The package then includes
the mdw file associated with the db and the setup creates an autmatic link to
it.

A good tip is to always keep a copy of the "blank" system.mdw file that is
loaded with Access. This makes development of a db easier since you can then
subscribe to this workgroup when designing so that you are not required to
log on each time when the db is opened. Later subscribe to the secure mdw for
distribution to other users.

Hope this helps. Rob

 

[Billy]

Joan, this is what I have on my target:

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\Documents
and Settings\david.scott\Desktop\Database2\DR Final06.mdb" /WRKGRP
"C:\Documents and Settings\david.scott\Application
Data\Microsoft\Access\System.mdw"

Hey check it out and please advise
Billy

 

[Billy]

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\Documents

and Settings\david.scott\Desktop\Database2\DR Final06.mdb" /WRKGRP
"C:\Documents and Settings\david.scott\Application
Data\Microsoft\Access\System.mdw

Somebody please help!

I need to put this to the network. I have done everything else,
including splitting the Database.

Billy

 

[Joan Wild]

I assume that DR Final06.mdb is the frontend and you have put the backend on
the server. Also copy the system.mdw in the path below to the server.

Now change your shortcut to
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE"
"C:\Documents
and Settings\david.scott\Desktop\Database2\DR Final06.mdb" /WRKGRP
"F:\something\somewhere\System.mdw"

Change the F:\something\somewhere... to reflect the *actual* drive and path
on the server - I can't see your computer, so you'll have to figure this out
for yourself - where on the server did you copy the system.mdw?

If you haven't put the backend on the server, you need to do that and then
open the frontend, go to Tools, Linked Table Manager, and refresh the links
to the backend *on the server*.

 

[Billy]

Joan et al,
I am back again. My project has turned out very well, thanks to Joan
and others. I was able to apply user level security features, split
the database and distribute it to the desktops. However, there are a
few areas I am concerned about.
1] The backend did not pick up security features
2] Security features applied to all access Database, such that I have
to log in anytime I am accessing one of these database.
3] It seems to me that security.mdw applied the whole access
application.
4] I distributed the mdb file but did not know how to distribute the
mdw file. I am working on this!

Looking forward to your feedback.
Billy

 

[Joan Wild]

Hi Billy:

1] The backend did not pick up security features

That would occur if you used the Database Splitter Wizard. You should have
split it manually. What you need to do now, is to secure the backend using
the same mdw that you secured the frontend with. i.e.
Start your database using the desktop shortcut. Hit Ctrl-O and open the
backend. Proceed to run the security wizard, choosing not to create a new
mdw (it will use the one in use for this session).

2] Security features applied to all access Database, such that I have
to log in anytime I am accessing one of these database.

You are joined by default to your secure mdw. Use the workgroup
administrator, and click on Join and rejoin the standard system.mdw that
ships with Access. It usually is located in the windows system folder, but
search for it first.

3] It seems to me that security.mdw applied the whole access
application.

The wizard likely made your custom secure workgroup, the default to use for
every session. Running the workgroup administrator and rejoining system.mdw
should solve this.

4] I distributed the mdb file but did not know how to distribute the
mdw file. I am working on this!

You need to put the mdw file and the backend mdb file in a location on your
server that all users have access to.

 

[Billy]

Thanks a lot Joann. I have been travelling the last two weeks.
I am back to the office, trying to catch up!
Now, here is what I need to do. I need to delete one data entry on the
form and be able to delete the rest of the data entry.
For example, the first entry on the form is Defective Part, the last
entry is Date Closed.
When I delete the Defective Part, I should be able to delete everything
else that was entered on this particular form, including the Date
Closed. How can I do this?
Billy

Hi Billy:

1] The backend did not pick up security features

That would occur if you used the Database Splitter Wizard. You should have
split it manually. What you need to do now, is to secure the backend using
the same mdw that you secured the frontend with. i.e.
Start your database using the desktop shortcut. Hit Ctrl-O and open the
backend. Proceed to run the security wizard, choosing not to create a new
mdw (it will use the one in use for this session).

2] Security features applied to all access Database, such that I have
to log in anytime I am accessing one of these database.

You are joined by default to your secure mdw. Use the workgroup
administrator, and click on Join and rejoin the standard system.mdw that
ships with Access. It usually is located in the windows system folder, but
search for it first.

3] It seems to me that security.mdw applied the whole access
application.

The wizard likely made your custom secure workgroup, the default to use for
every session. Running the workgroup administrator and rejoining system.mdw
should solve this.

4] I distributed the mdb file but did not know how to distribute the
mdw file. I am working on this!

You need to put the mdw file and the backend mdb file in a location on your
server that all users have access to.

 

[Joan Wild]

Thanks a lot Joann. I have been travelling the last two weeks.
I am back to the office, trying to catch up!
Now, here is what I need to do. I need to delete one data entry on
the form and be able to delete the rest of the data entry.

I'm sorry, I can't figure out what you mean. What is a 'data entry'? A
record, a single field?

For example, the first entry on the form is Defective Part, the last
entry is Date Closed.

Are these fields or records?

When I delete the Defective Part, I should be able to delete
everything else that was entered on this particular form, including
the Date Closed. How can I do this?

Data is stored in tables, not forms. Forms are just a presentation for the
user to interact with the data in the tables.

Can you describe your table(s)? Are the Defective Part and the Date Closed
in the same table; the same record? How are they related?

 

[Billy]

I am sorry that I was not very clear. I meant fields on the form.
After updating the forms, I would like to go back and deleting all the
information by just a single delete event on the first field. Not all
the fields are linked to one table.
HTH

 

[Joan Wild]

I wouldn't want a record to get deleted when the contents of one control get
deleted - one might easily just be editting that one control and not want
the whole record to get deleted!.

The standard method to delete a record is to click on the record selector
(the vertical grey bar to the left of the record), and then hit the delete
key on the keyboard. Another method is to choose Edit menu, Delete Record
(or hit the corresponding toolbar button).