Jim Lawrence
accessd at shaw.ca
Sat May 30 11:02:02 CDT 2009
May he secure many grants... :-) Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: Saturday, May 30, 2009 7:01 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Password on the Backend I actually prompt the user for the password on sign in and store it in a global variable. It's a database full of patient/medical info so the doc needs it to be a bit more secure. Interesting db, BTW. He's a pediatric endocrinologist at Rady Children's Hospital in San Diego. Treats kids - mostly diabetics. If he can get the data, he can do lots of slicing and dicing - epidemiological studies - find out what works, what doesn't. And hopefully get some grant money to keep paying his programmer. :o) Rocky -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey Sent: Saturday, May 30, 2009 5:22 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Password on the Backend I did this a year ago Rocky. It works well. As you've found out you have to provide the pw when linking or relinking tables but not thereafter. Of course when you, as developer, open the BE direct you also have to give it. Also, if you use OpenDatabase to open the BE directly in code (say to do an indexed Seek) then you'll need to provide the pw there too but the trick there is to get the pw from the connection string of a linked table and then supply that in the OpenDatabase statement. That way the pw doesn't need to be in your code anywhere. Andy -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: 30 May 2009 00:22 To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Password on the Backend Me neither. That's why I avoid using it. Rocky -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Friday, May 29, 2009 4:00 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Password on the Backend Well there you are... Your smarter than me... I am not a Access security guru. ;-) Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: Friday, May 29, 2009 2:59 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Password on the Backend I found the answer on-line. Relink the tables, then Access 'knows' the password. Too simple. Rocky -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka Sent: Friday, May 29, 2009 2:40 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Password on the Backend Rocky, instead of putting a password on the backend, why not use Access User level security? If you use the same .mdw for the front and back end, when a use logs into the FrontEnd with a valid Username and Password, Access will automatically use those credentials on the backend. Just a thought.... Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: Friday, May 29, 2009 3:19 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Password on the Backend Dear List: I put a password on the back end and prompt for it in a pop-up in the opening form. However, now when I click a command button to open another form I get an 'invalid password' error. It doesn't look like the _Open event of the called form is executing. But the form is bound to tables linked to the back end. Does the OpenForm need a password parameter? Or what am I missing here? MTIA Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com <http://www.e-z-mrp.com/> www.bchacc.com <http://www.bchacc.com/> The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com