How do I turn off user level security or distribute it?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I activated the user level security and now the only version that will run is
the one on my desktop. How do I turn off user level security and distribute
the program or how can I distribute the program with the user level security
still in place?

Thanks
 
If you want to keep it in place, all you should need to do is to copy all of
the related files (the secured database, the shortcut to it, the workgroup
file named something along the lines of "Secured," etc.) into a folder that
all of your users will be able to access. If you have to deliver it to
separate users without some kind of network, just copy the files to some
folder on their computer. Be sure to double check the target of the shortcut
so it points to the right place.

If you decide to go without security, just delete the secured database,
delete the "Secured" file, and rename the backup (.bak) file to a .mdb file.

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy
 
Paul (ESI) wrote:

(snip)
If you decide to go without security, just delete the secured database,
delete the "Secured" file, and rename the backup (.bak) file to a .mdb file.
Click to expand...

Um, I'd be careful of suggesting that. There's no guarantee that he
used the wizard (to create a .back file), or that the .bak file still
exists (he might have deleted it). IOW the secured db could be the only
one that he actually has!

It's never wise to suggest that people delete things, IMHO.

Cheers,
TC
 
I agree, and I still have the original, the security and the .bak files. In
fact everytime I have made a change I have kept each in a separate folder. A
little overkill probably.
 
Well, I did say "If you decide to go without security, just delete the
secured database, delete the "Secured" file, and rename the backup (.bak)
file to a .mdb file." Now, why would anybody just go willy-nilly deleting
things like crazy? I don't know. Maybe I am over-estimating folks, but I
would think my statement above would lead to the obvious assumption that you
NEED the .bak file to still exist in order to do pull this off properly, so
you should make sure you still have it. I mean, isn't that kind of just
common sense?

If you told me "In order to have your new version of your ISP keep your old
features, download the new version, then delete the old version and install
the new one," am I going to delete the old version without first making sure
I definitely downloaded the new version? (Weird example, I know, but it was
the best that came to mind.)

Good point, though, about the fact that he may not have used the wizard. I
suppose I'm just so used to using it that I forgot that you don't
neccessarily get a backup file without it, unless you do it yourself.

I don't know. Maybe I'm crazy here, but I just kinda figured that the
typical person on this board would know better than to preview all
instructions before following them all, especially when it comes to deleting
things. I suppose, the directions would be better reversed, though. "Rename
the .bak file to a .mdb, then delete the secure database, etc." That way, if
I AM over-estimating common sense, they'd see that step first, and make sure
they still have the proper files.

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy
 
Sorry, I still say it is bad advice to advise someone to delete a
critical file, in circumstances where you do not know /for sure/
whether they do or do not have a backup!

It's like: "I've prescribed drug ''x', I know it has a serious adverse
consequence in combination with drug 'y', but I guess they'll read the
instructions, so I need not warn them myself".

Cheers,
TC
 
Yes, I definitely do see what you mean. I answered a similar (basically the
same) question in a later post and I think I did better there. I see what you
mean, I guess my mistake was assuming that it was kind of obvious that you
need to make sure you still have the backup before you go deleting stuff. I
suppose a lot of folks might not think to do that, and that would end up very
bad if they did not still have a backup.

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy
 
Oooooo. For future reference, please keep the .bak file. If you no longer
have the .bak file, but you want to remove security, you may be able to do
so. If you can still get into the database, (one of the username/password
combos you used works, let's you in, and gives you the proper rights) you can
recover it. The only problem is, if your database has gotten really big (a
lot of tables, queries, reports, etc.) it will be a major pain in the butt.

What you could do is create a new database, then copy all of the tables,
queries, reports, etc. over to the new database. Access doesn't let you
select a big group of objects to copy at once. You have to copy them one at a
time, so you can see how this gets to be a pain if you have a lot of stuff.

Once you are finished copying, make sure each object works properly. Make
sure this new database is literally like a new unsecured copy of the existing
one. Once you are sure, and you are sure you no longer want or need the
secured version, delete the secured database, the workgroup file probably
named something like "Secured," and the shortcut. If you wish, once the old
database is deleted, you can rename the new database to the same name as the
old. Just be sure you wait to do so until you delete the other.

I hope this helps. There may be an easier way to unsecure a database if
you've accidentally deleted the .bak file, but I don't know it. If there is a
way, and somebody knows, please post here. I'm sure you'd be helping a lot of
people with that answer.

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy
 
Paul (ESI) said:
Oooooo. For future reference, please keep the .bak file. If you no longer
have the .bak file, but you want to remove security, you may be able to do
so. If you can still get into the database, (one of the username/password
combos you used works, let's you in, and gives you the proper rights) you
can
recover it. The only problem is, if your database has gotten really big (a
lot of tables, queries, reports, etc.) it will be a major pain in the
butt.
Click to expand...

No it isn't. Login in as a member of the Admins group. Grant full
permissions to all objects (don't forget the database object) to the Users
Group.

Rejoin the standard system.mdw that ships with Access. Close Access and
reopen it (should get no login). Create a new mdb and import all objects
from your old mdb (use File, Get External Data, Import).
 
Cool! I thought there might be an easier way, but I didn't know it. Thanks,
Joan. This is good information for everybody.

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy
 
Joan thanks for your input (You too Paul!!!)

Joan I have a couple of further questions...

1. How do I rejoin the standard System.mdw to the data base????
2. If the data base is split (BE/ FE) how will this effect the back end?
Will I still be able to link the BE & FE????
3. I have given the "User" group full permissions to everything (Tables,
queries, forms, reports ETC ETC) I am assuming that is what you meant??

Thanks again for your input.
 
TC said:
I rest my case, your honor!

TC :-)
Click to expand...

LOL. Yeah, yeah, okay, but Sam also proved my point. Sam knew that the .bak
file was no longer available, so it isn't as though the user in this case
would have just gone deleting stuff without making sure they had the .bak
file first. Still, you make a darn good point, which is why I've modified my
advice when this question comes up again, as you can see in a later post
after the one in question. Thanks, TC. ;-)

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy
 
Sam said:
Joan thanks for your input (You too Paul!!!)

Joan I have a couple of further questions...

1. How do I rejoin the standard System.mdw to the data base????
Click to expand...

I've lost track of what version you are using. So if it's 97 or 2000 use
Start, Run, wrkgadm.exe and then Join the standard system.mdw (it's usually
located in the windows system folder, but search for it first). If you're
using 2002 or 2003, then open Access and go to Tools, Security, Workgroup
Administrator.

2. If the data base is split (BE/ FE) how will this effect the back
end? Will I still be able to link the BE & FE????
Click to expand...

You would need to remove the security on the BE as well. i.e. follow the
steps I outlined before.
3. I have given the "User" group full permissions to everything
(Tables, queries, forms, reports ETC ETC) I am assuming that is what
you meant??
Click to expand...

Yes it is - don't forget the database object.
 
I boobed recently in a discussion in another group, on how to identify
the default browser. So I am jumping harshly on everyone else, to make
up for that!!

Cheers,
TC
 
LOL! I see. Well, I didn't really think you were "jumping harshly" on me.
Just a fair and constructive criticism that was quite helpful. Hey, no sweat,
though. Pobody's nerfect.

--
Have a nice day!

~Paul
Express Scripts,
Charting the future of pharmacy
 
Back
Top