Dane,

regarding your instructions, number two states:Therefore, should I only import the "Custom Security" module to the BE and run the "CreateSecurityTables" script, and import all other items, in number one of instructions, to the FE? Will the forms, in the FE, link to the created tables in the BE, or might I need to link them?

Thanks

this is my first post ever and i wanted to say thanks to dallr for a great job on the custom security. everything works great on the computer i use at work (a2010), though i haven't tested all aspects. i was just introduced to a2010 and am still recovering. when i take my work home and copy my database from my flash drive and try to open the db i get an error telling me that i'm missing a reference or a link is broken to file mscomct2.ocx. any help is always appreciated.

dallr

i'm sorry, i didn't address this to anyone. here it is again.

this is my first post ever and i wanted to say thanks to dallr for a great job on the custom security. everything works great on the computer i use at work (a2010), though i haven't tested all aspects. i was just introduced to a2010 and am still recovering. when i take my work home and copy my database from my flash drive and try to open the db i get an error telling me that i'm missing a reference or a link is broken to file mscomct2.ocx. any help is always appreciated.

Dane, I updated your instructions (attached), based on more information I have found utilizing a pre-split database, and Access 2007.

Hi:

The update new controls only found (6) reports of more than 20 defined on the FE Database and (0) forms of more than 20 defined dont know what really happend.

Excellent, Excellent code and is working fine on Access 2007 with the (6) reports found. Manually added a form and a control and the field was not enabled to that user.

I have a bunch of forms with a lot of fields (controls) but the only way to not allowing any access to a user to that form is to enter all the fields (controls name)?

There's any way to disable an access to a form without entering all the form controls?

Thanks,
Robert

I've just attempted to run step 2a from your HOW TO - the section on running the CreateSecurityTables.
I get the compile error, "Expected user-defined type, not project" at this line:

Public Sub ChangeProperty(db As Database, strPropertyName As String, varPropertyType As Variant, varPropertyValue As Variant)

I've looked up the error elsewhere and microsoft suggests "Remove the references to the non-automatable interfaces from Project References." which apparently are one of these two libraries : MSVSA Event Source Installer 1.0 Type Library & MSVSA Inproc Event Creator 1.0 Type Library.
Neither of these are enabled let alone available on my system.

Any Thoughts?

EDIT: I've narrowed it down to the declaration db As Database. If I remove this, the compile runs fine. Is there another way I can declare the Database?
EDIT2: Got it. Ground and Pound! I set the declaration as DAO.Database. Likely cause: conflict with an ADODB library.

This post has been edited by Squire4Hire: Jan 13 2011, 12:02 PM

Found a bug:

The SecurityEnabled function doesn't like lines being drawn on the form. It halts here when it comes across my Line30 control with an error: "Error Number 438. Error Description Object doesn't support this property or method."






Just thought you might like to know.

Dane, is there any reason, you know of, that this would not be adaptable to include access control of tables / fields? I think it would be awesome to somehow integrate your database functions with that of Allen Browne's here. I would like to take the table locking properties of Allen's form ("frmAttribUser") and add the user group's of your database functionality as an additional option in the form, as an additonal way to lock tables. I looked at Allen's code, but I cannot figure out how to add this functionality, as I am not very experienced with programming / VBA code writing.

Thanks again!

This post has been edited by bg3075: Jun 30 2011, 10:27 AM

Dane just wanted to say thanks again for picking up the slack that MS left behind when they did away with the USL.

Problem with windows 7:
I have been using your password program for over a year in our fire dept. and it has worked great. The problem I have now is that we had to replace one of our computer in our network and it has windows 7 on it. All the other computers were XP. The new computer will open up the log in field and let you fill out the user name and password, but will not do anything else. It just toggles back and forth between the two fields. It will not even let you close the data base using your exit button. I have to “X” out of the program entirely to close it.
I can back door it using the shift option, but as we know that defeats the purpose. Any help will be greatly appreciated.
I have noticed that you have not put a post in a while so I hope this will find you.

Awesome program, so far. I'm using Access 2010 on Windows 7 x64. Everything works up to "Update New Controls" from frm_Administrator. I get an error message Microsoft Access error 32641: "You cannot open the database object "report name" in design mode with the current settings." I've searched everywhere looking for a meaning to this error message and there is nothing on error 32641 anywhere. Anyone have an idea what this might mean or what might be causing it?

Thanks for your help.

Allen

Many thanks for these files - I'd been looking for an easy way to implement user security and this has certainly worked wonders. Running Windows 7 (x64) and Access 2010, having built a brand new db in 2010, (and admittedly not tested exhaustively) but so far all the security seems to be working fine.

Thanks again.

This post has been edited by exvkg: Oct 11 2011, 11:47 PM

It's been a while since I posted here as I was/am in a job function that didnt need me to make/adjust Access db's


I have a question....if I split my database...1) will this method still work, and 2) what impact might it have....and I am thinking of adding auditing to my database as well, any concerns that I need to be aware of there as well

I am using Access 2007, BE will be on a networked drive that all users already have read/write ability

Thanks

This has been INCREDIBLY helpful! I've been looking for a solution for the last few weeks. Thank you!

Would this work for a DB that already is using MS Access security? Per my client's request i need to make certain fields read only and only people in the Admins security group will be able to edit these fields.

Thank you for your assistance!

This was incredibly helpful!!! The only issue I have, is trying to make an MDE file. Everything compiles correctly, I walked through all of the steps that were recommended in the links, and the screen pops up for the userid and password, but when you hit enter, nothing happens. Does anyone have any suggestions?

This program is great, but I was wondering if there is any way to make it so that users can only view records that they added? I've been looking through the logic and I'm not sure what I would do to do that.

Each table has a field "AddedBy" that defaults to the current user name, but I'm not sure what the next step is.

Nick

nick,

I have set up something similar while implementing this piece of application for a Time Tracking Database in my office. It has taken me a fair chunk of time and effort to have it do what I need it to but I can give you a brief breakdown of how I'm doing it and maybe it will help you with your project.

1. When the application loads, I authenticate the Windows username against a userlist in the database - I do this instead of assigning usernames and passwords to each user, though it still requires the user adding and setup as per Dallr's system. When this authentication is deemed valid, I place the user name, userID, current date and a few other items into a Local Table that isn't shared on the back end. This allows for each user of the database to have their identifying information stored locally and to search accordingly. All other tables are linked to a back end.

2. Once the local table is populated with the proper data about the user, my relationships/linking ensure that only that single users records are shown in any query or form/subform links. And because there is only ever one record in that table there shouldn't be a mixup. Essentially, all records are stored with the UserID to inform who it belongs to - very much like your AddedBy field.

I'd say that the Local Table is the key to it all - at least how my database works.