How to prevent DB object from being imported to another DB 1

[Jedi420]

I was recently reading foolio12's security FAQ (faq181-3893) and I am quite satisfied with the level of security that my DB has, except for one thing. You can open a new DB and just import all my tables and queries and since my tables are linked, whomever would do this could alter/delete critical data. Is there a way that anyone know's in which I could restrict someone from doing this. My DB does rely on importing and exporting so this may complicate the issue. Any ideas or suggestions anyone had would be most appreciated. Thnx! (^_^)


-Jedi420

A man who has risked his life knows that careers are worthless, and a man who will not risk his career has a worthless life.

 

[JeremyNYC]

Jedi,

If that is the case, then you have not properly implemented security. If you have properly implemented security you will need to be logged in as a user (who is a member of a group) with sufficient security to link to tables. I promise this is true. I'd make a backup and resecure the database.

Jeremy

==
Jeremy Wallace
AlphaBet City Dataworks

http://www.ABCDataworks.com

Professional Development for Clients Large and Small

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.

 

[Jedi420]

Hey Jeremey,

:-D I know that I didn't properly implement security. I kinda faked it in that it's nearly impossible to edit anything (tables, forms, queries, etc.) ... only thing is my problem mentioned above, which I guess has no other solution than to properly implement security. My boss, for some reason, doesn't want to have to 'log in' to the database so I've been doing what I can to secure it anyways. I was pretty impressed of what I've achieved so far ... the shift button and F11 are disabled, the front end is an mde, no one can change the properties of any form, nor can they edit code (they cant even bring the code window up since all the special keys are disabled).

It's just that someone could alter/delete my data from an outside DB that imported my linked tables. I'll talk with my boss, but are you certain there is no way around this besides setting up "real" security, which I've done before, but I can't go against my boss's requirements? Thnx for responding! (^_^)

-Jedi420

A man who has risked his life knows that careers are worthless, and a man who will not risk his career has a worthless life.

 

[JeremyNYC]

Jedi,

I sympathize with you--having a boss who wants a secured database but does not want to have to log in has got to be frustrating. I'm not sure what to tell you. You could, though I wouldn't think it highly advisable, fully secure your database and give your boss a shortcut to the database that contains his user name and password.

I would not do this, mostly because I agree with your sig file--I value my own integrity too much to tell someone I can build him a database that is secure without requiring logging in.

Just to be clear, I don't mean to be aiming any of my acid at you, I just feel for you having to navigate such waters.

Jeremy

==
Jeremy Wallace
AlphaBet City Dataworks

http://www.ABCDataworks.com

Professional Development for Clients Large and Small

Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.

 

[Jedi420]

Jeremy,

Thanks for the advice. I appreciate it. I think I'm gonna try to convince him to at least let me force people to log in. I just really want to protect my data from outside sources. Of course, if someone is determined enough, they'll get in no matter what, but I'd like to make the cost of getting in more than the data is actually worth. You've helped me out plenty of times ... They only let me give you 1 star instead of 2, but you deserve a helluva lot more. Thnx a bunch! (^_^)

-Jedi420

A man who has risked his life knows that careers are worthless, and a man who will not risk his career has a worthless life.