A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Login Form



 
 
Thread Tools Display Modes
  #1  
Old December 9th, 2006, 10:02 PM posted to microsoft.public.access.tablesdbdesign
accessuser via AccessMonster.com
external usenet poster
 
Posts: 66
Default Login Form

I have frmpassword for all 13 depts, however I feel it might not be a good
for the long run. so I want to change to store my dept names and password
into a table. I read many posts and did a lot of research, but can't seem to
find a map for this problem.

I want to have a tblpassword with fields name of "department" "password" and
the third field i want something like if users input the dept and password
correctly, open their dept page.

Do I need to run a query for this? if so, how and what are the settings that
i need to do? Can someone give me some detail explaination.


Thank you!

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200612/1

  #2  
Old December 10th, 2006, 06:00 AM posted to microsoft.public.access.tablesdbdesign
John Vinson
external usenet poster
 
Posts: 4,033
Default Login Form


"accessuser via AccessMonster.com" wrote:

I have frmpassword for all 13 depts, however I feel it might not be a good
for the long run. so I want to change to store my dept names and password
into a table. I read many posts and did a lot of research, but can't seem to
find a map for this problem.


Well, there aren't many maps because what you're doing is quite unusual, and
I'd almost have to say offtrack.

Rolling your own, nonstandard, private security system is a major and
complex undertaking; and - unless it's layered behind Access Workgroup
security - can be readily cracked by anyone with a modicum of expertise in
Access. It's MUCH harder to do this well than it is to implement workgroup
security.

The latter isn't perfect by any means, and can be hacked, though in practice
I haven't heard of many such instances. It's also complex, but securing a
database flexibly and effectively is simply a complex task and requires a
complex tool.

Have you tried using the standard security model (which could easily let you
use ONE form for all thirteen departments, based on a query selecting just
that department's data)? Have you consciously rejected it? If so, why?


--
John W. Vinson[MVP]



  #3  
Old December 11th, 2006, 01:07 AM posted to microsoft.public.access.tablesdbdesign
accessuser via AccessMonster.com
external usenet poster
 
Posts: 66
Default Login Form

Thanks John,

After a whole day research and playing with the code, I finally figured out
how to make it simpler and better. I create a frmlogon using information
base on a table, if match then open the forms assigned to that particular
dept. It is working great!!!!!! I got the code from the following site,
anyone who experiences same problem, might be worth it to take a look at it.

http://www.databasedev.co.uk/login.html

Thanks for mentioning about getting value from query. I was using table, but
changed to query. I wish I had known it long time ago, I had spent so much
time creating 13 different forms and linking them ....well, I learn from it.

Acutally I have another question now, but I will start a new post.

Thanks so much.

John Vinson wrote:
I have frmpassword for all 13 depts, however I feel it might not be a good
for the long run. so I want to change to store my dept names and password
into a table. I read many posts and did a lot of research, but can't seem to
find a map for this problem.


Well, there aren't many maps because what you're doing is quite unusual, and
I'd almost have to say offtrack.

Rolling your own, nonstandard, private security system is a major and
complex undertaking; and - unless it's layered behind Access Workgroup
security - can be readily cracked by anyone with a modicum of expertise in
Access. It's MUCH harder to do this well than it is to implement workgroup
security.

The latter isn't perfect by any means, and can be hacked, though in practice
I haven't heard of many such instances. It's also complex, but securing a
database flexibly and effectively is simply a complex task and requires a
complex tool.

Have you tried using the standard security model (which could easily let you
use ONE form for all thirteen departments, based on a query selecting just
that department's data)? Have you consciously rejected it? If so, why?


--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200612/1

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 07:14 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.