Security problems

[Bob Hughes]

I have 2 major problems with a secured DB. For ease of testing both FE & BE
are on the same server, which I have done before with no problems.

Everything works fine from my computer. The users groups has no permissions
on the FE. It will not run on my computer without joining the workgroup and
logging in. Also the startup is set to not display the database window

I moved everything to the company's server. When I use them through VPN the
permissions are as they should be & I cannot access the FE without logging
in. When I do login the DB is not visible.

BUT the users can run and use the db using their default workgroup file?
They also are using win2K & Office 2K

One user, using my link file, with the proper workgroup file sees two
windows on the status bar after logging in. When he clicks on one he sees
the database.

Does anyone have an idea about either of these problems. I would really
like to resolve this from home.

Bob

 

[Grumpy Old Man]

BUT the users can run and use the db using their default workgroup file?

Hi Bob,

If this is true then you've missed a step in securing your app. Have you
followed the MS FAQ to the letter? There's a link to it on my web site and
there's also a step-by-step example that may be of use.

As always, work on a *copy* of your files.

Regards,
Keith.
www.keithwilby.com

 

[Bob Hughes]

Hi Bob,

If this is true then you've missed a step in securing your app. Have
you followed the MS FAQ to the letter? There's a link to it on my web
site and there's also a step-by-step example that may be of use.

As always, work on a *copy* of your files.

Regards,
Keith.
www.keithwilby.com

Keith,

I did not quit follow your method, but used what is in the SECFAQ.doc. In
other words I used the security wizard to create my secure DB.
This DB works, as it should on my computer. If I do not join the proper
workgroup I cannot open the DB.
You must be right & I probably missed a step but I don't understand how
the security seems in effect on my PC but not on others.
I'll do it over your way.

The answer to my second question was easy. Someone held down the shift
key

Bob

 

[Rick Brandt]

news:[email protected]:

I did not quit follow your method, but used what is in the
SECFAQ.doc. In other words I used the security wizard to create my
secure DB.
This DB works, as it should on my computer. If I do not join the
proper workgroup I cannot open the DB.
You must be right & I probably missed a step but I don't understand
how the security seems in effect on my PC but not on others.
I'll do it over your way.

Something doesn't make sense here. If you have to use a particular mdw on
your pc to open the file then everyone else should have to use a particular
mdw file as well. Unless you somehow got things backwards where all mdws
can open the file *except for* one that you have on your PC. Is the one
that does NOT work on your PC named "System.mdw" and the one that does work
named something else? (that's how it should be)

 

[Bob Hughes]

Something doesn't make sense here. If you have to use a particular
mdw on your pc to open the file then everyone else should have to use
a particular mdw file as well. Unless you somehow got things
backwards where all mdws can open the file *except for* one that you
have on your PC. Is the one that does NOT work on your PC named
"System.mdw" and the one that does work named something else? (that's
how it should be)

Your right and I am getting very confused. On my computer(1) using the
default system.mdw the DB is protected. I go to another computer(2) and
use its "System.mdw"and open the DB across the net, it is not protected.
I copied the "System.mdw"from PC2 to PC1 and the db is still protected on
my computer(1)using that workgroup file from (2). As far as I know I
followed all the steps in the SECFAQ.

On my computer when i join my new workgroup file and log in as admin, my
password works but I can not use the Db, which is how it should be
because it only belongs to the users group.

And this was only supposed to take me 1 hour :-(

Bob

 

[Keith]

Your right and I am getting very confused. On my computer(1) using the
default system.mdw the DB is protected.

You should leave system.mdw unmodified and create a new mdw for exclusive
use by your app.

I go to another computer(2) and
use its "System.mdw"and open the DB across the net, it is not
protected.

This is what leads me to suspect that you've missed a step. On your PC,
look at the permissions for the "Database" object. I think the "Users"
group may have permissions granted.

I copied the "System.mdw"from PC2 to PC1 and the db is still
protected on my computer(1)using that workgroup file from (2). As far
as I know I followed all the steps in the SECFAQ.

Are you sure that you're using system.mdw? What is in the shortcut command
line?

Regards,
Keith.
www.keithwilby.com

 

[Bob Hughes]

Well this has been a real challenge. I have 2 computers both with win2K
and Office97 and Office2K. Computer 1 is my main machine and 2 is an old
slow machine but good for testing. I believe I have discovered my
problems, but not why. I have been using the wrong "system.wdw"on PC1. I
used the one in "system32" instead of the one in "\Program Files\Common
Files\System" This led my PC1 to think the file was secure, while PC2 was
using the correct one & found file not secure.

From PC1 I used "D:\Program Files\Microsoft Office 2000\Office\1033
\WRKGADM.EXE" to create new workgroup file. Results not secure

From PC1 I used user-level security wizard to create secure DB. Results
appear secure. Both PC's think so. I will put new secured files on
company server tonight & keep my fingers crossed.

I do not know why all this is happening but right now I don't care as
long as I can make it work.

One thing that has helped in all this, is I created a seperate program
that allows me to add, remove and change passwords while displaying
current workgroup users & groups.

I'll be glad to share this with anyone. It was this group that gave me
the information to create it in the first place.

Bob

 

[Keith]

I have 2 computers both with win2K
and Office97 and Office2K.

There are known issues with version co-existance on the same PC. I can't
recall what they are off the top of my head but it might be worth your
doing a Google search.

Regards,
Keith.