Security Permissions and Access

[Porisius]

Hello all,

I have a problem with one of the databases I wrote a long time ago, kinda been out of the loop so bear with me. I wanted to update it a bit since I haven't used it in a long time.

Recently my work migrated over to WinXP, and ever since my database has not been able to open due to a permissions related problem. It still works on a Win2000 box, but our ITs already ditched them.

I have Full Control, Ownership, and even my ITs can't open it under their admin accounts with ownership/full control too.

The database does check for the Windows username as a security option, and has VB into it. However, it's not executing the script I wrote. So, I don't know if that is the problem or not. Doubt it personally. It says "Please check with system administrator." not database admin like I wrote. So, I do know that it isn't my script, even then I could open it in read-only and get in the back door.

Unfortunately with the way my work's network is setup, emailing it to the internet is not an option.

If you guys have ANY ideas/clues/suggestions, please let me know. Thanks.

 

[Banana]

Hmm, I need to make clear what we are dealing with.

Are we using User Level Security here? Or was it a DIY security solution, or combination thereof?

Next, can you bypass it by holding down the shift?

 

[Porisius]

Unsure, I do know from what I have seen is that it's something that Windows doesn't like to see running based on what is, I presume, told not to run. I am just curious if there is anything that I can do to prehaps edit the actual file since Notepad/Wordpad seem to corrupt it if I try to do that.

Even still, if the database was going to attempt to keep me out, opening it up in read-only in the past has for sure allowed me into without executing the script to kick me out. Also, like I said, if it was a database thing, I would have known.

Well, its 11 PM where I am, and I will try the shift thing tomorrow. Thanks for the swift reply, Banana. I'm afraid, unfortunately, am not expecting to get this to work, although if it does, it's a nice treasure to have back, and knock off some of the rust of the programming I once knew.

 

[Banana]

Well, for one thing, I wouldn't dare to edit the .mdb outside of Access or proper channel (e.g. automation via DAO or ADO library).

If you had to go to that length just to read the data and not get script kick you out, then there is something amiss. You'd need to talk with the developer of the application and work out the proper route to get the data without getting kicked out.

 

[RossWindows]

I know this is a little old, but I'm not sure if you ever got this working.

When you say;

I have Full Control, Ownership, and even my ITs can't open it under their admin accounts with ownership/full control too.

Are you referring to the .mdb file itself or the parent folder where it resides?

This almost sounds like you applied Full Control to the file but not it's parent folder. You HAVE to give full control to both.

You could always email it to one of us and we can try and break into it.
I've corrupted and locked myself out of many a database but have always found a way to extract the data and recover.