I want to have a password that will change for each month. If I had a table
with a field of 'Month' with the number of the month and another field
called 'Password' that had twelve records. What would be the best way of
looking at the current date and then, if it was say February, picking the
password that was against the number 2 in the Month field.
dixie 13 1390
dixie wrote: I want to have a password that will change for each month. If I had
a table with a field of 'Month' with the number of the month and another
field called 'Password' that had twelve records. What would be the best
way of looking at the current date and then, if it was say February, picking
the password that was against the number 2 in the Month field.
dixie
tblP
MonthID P
1 MLKJr
2 BMyValentine
3 bean239
4 prlfls
5 mmmysdy
6 dddysdy
7 ahatfoj
8 nohldy
9 tmstrs
10 gstsngblns
11 trkygblr
12 ntvty
SELECT P FROM tblP IN 'G:\HiddenDirectory\P.mdb' WHERE MonthID =
Month(Now());
This may not be the best way but it should work. Don't use Month for a
field name since it's a reserved word. MonthID is of type Long.
James A. Fortune
I see you use a different database in a hidden folder to put the passwords
in. What about just a hidden table say USysPW?
dixie
<ji********@compumarc.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com... dixie wrote: I want to have a password that will change for each month. If I had a table with a field of 'Month' with the number of the month and another field called 'Password' that had twelve records. What would be the best way of looking at the current date and then, if it was say February, picking the password that was against the number 2 in the Month field.
dixie
tblP MonthID P 1 MLKJr 2 BMyValentine 3 bean239 4 prlfls 5 mmmysdy 6 dddysdy 7 ahatfoj 8 nohldy 9 tmstrs 10 gstsngblns 11 trkygblr 12 ntvty
SELECT P FROM tblP IN 'G:\HiddenDirectory\P.mdb' WHERE MonthID = Month(Now());
This may not be the best way but it should work. Don't use Month for a field name since it's a reserved word. MonthID is of type Long. James A. Fortune
I guess my previous post was just a rhetorical question, as both would work.
Thanks for your help james. It is just what I needed.
dixie
"dixie" <di***@dogmail.com> wrote in message
news:41********@duster.adelaide.on.net... I see you use a different database in a hidden folder to put the passwords in. What about just a hidden table say USysPW?
dixie
<ji********@compumarc.com> wrote in message news:11**********************@z14g2000cwz.googlegr oups.com... dixie wrote: I want to have a password that will change for each month. If I had a table with a field of 'Month' with the number of the month and another field called 'Password' that had twelve records. What would be the best way of looking at the current date and then, if it was say February, picking the password that was against the number 2 in the Month field.
dixie
tblP MonthID P 1 MLKJr 2 BMyValentine 3 bean239 4 prlfls 5 mmmysdy 6 dddysdy 7 ahatfoj 8 nohldy 9 tmstrs 10 gstsngblns 11 trkygblr 12 ntvty
SELECT P FROM tblP IN 'G:\HiddenDirectory\P.mdb' WHERE MonthID = Month(Now());
This may not be the best way but it should work. Don't use Month for a field name since it's a reserved word. MonthID is of type Long. James A. Fortune
dixie wrote: I guess my previous post was just a rhetorical question, as both
would work. Thanks for your help james. It is just what I needed.
dixie
I like your idea. Would an .mde effectively bury the password
information to the user?
James A. Fortune
I am doing it in an mde file and I have locked the program so you can't hold
the shift key down and open it. It is as close to secure as I can make it
without applying Access security which I don't want to do. I am going to
try to extend the idea to more than 12 possible passwords by using the
datediff function - I haven't quite got around to it yet, but I am going to
look at how I might do it. I'm thinking 365 possible passwords so that the
password automatically changes each day.
DateDiff("d",[StartDate],[EndDate]) will generate the number of the day and
I will somehow make this lookup a password. for that day. I am sure I can
use something like your last suggestion.
dixie
<ji********@compumarc.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com... dixie wrote: I guess my previous post was just a rhetorical question, as both would work. Thanks for your help james. It is just what I needed.
dixie
I like your idea. Would an .mde effectively bury the password information to the user?
James A. Fortune
dixie wrote: I am doing it in an mde file and I have locked the program so you
can't hold the shift key down and open it. It is as close to secure as I can
make it without applying Access security which I don't want to do. I am
going to try to extend the idea to more than 12 possible passwords by using
the datediff function - I haven't quite got around to it yet, but I am
going to look at how I might do it. I'm thinking 365 possible passwords so
that the password automatically changes each day. DateDiff("d",[StartDate],[EndDate]) will generate the number of the
day and I will somehow make this lookup a password. for that day. I am sure
I can use something like your last suggestion.
dixie
I've applied Access security before and completely understand why you
don't want to use it unless it's absolutely necessary. Format(Now(),
"y") will give a number from 1 to 366 (leap year). Also, when you
create your password table, leave the ID field off until the end. Then
apply it as an autonumber, save, and then change it to Long and to a
primary key. That way you don't have to type in all those pesky
numbers. I remember that you once dealt with importing tables from
other databases so you have probably considered this possibility with
the mde.
James A. Fortune
Thanks James, that one is better still, as I only had 12 passwords
originally. I have applied your expression to a table with 366 passwords
that are then concatenated with other information to give a daily password.
I also used Left$ and Right$ on them so that if anyone ever finds the table,
it still wont give them the password. The only other thing I will look at
here is that at the end of the year, to somehow scramble the passwords so
the passwords for next year are different for the same day than they were
this year.
Thankyou for your helpful ideas.
dixie
<ji********@compumarc.com> wrote in message
news:11**********************@c13g2000cwb.googlegr oups.com... dixie wrote: I am doing it in an mde file and I have locked the program so you can't hold the shift key down and open it. It is as close to secure as I can make it without applying Access security which I don't want to do. I am going to try to extend the idea to more than 12 possible passwords by using the datediff function - I haven't quite got around to it yet, but I am going to look at how I might do it. I'm thinking 365 possible passwords so that the password automatically changes each day. DateDiff("d",[StartDate],[EndDate]) will generate the number of the day and I will somehow make this lookup a password. for that day. I am sure I can use something like your last suggestion.
dixie
I've applied Access security before and completely understand why you don't want to use it unless it's absolutely necessary. Format(Now(), "y") will give a number from 1 to 366 (leap year). Also, when you create your password table, leave the ID field off until the end. Then apply it as an autonumber, save, and then change it to Long and to a primary key. That way you don't have to type in all those pesky numbers. I remember that you once dealt with importing tables from other databases so you have probably considered this possibility with the mde.
James A. Fortune
dixie wrote: .. I also used Left$ and Right$ on them so that if anyone ever finds the
table, it still wont give them the password. The only other thing I will
look at here is that at the end of the year, to somehow scramble the
passwords so the passwords for next year are different for the same day than they
were this year.
Thats's a very clever idea, Dixie. You could keep the same passwords
the next year and vary whether Right or Left is used and vary how many
characters are used. Mid(s) would really mess with their minds :-).
James A. Fortune
Actually, just concatenating the 1st and last digits of the year into the
password somewhere would work. Mine already have numbers in then, so nobody
would guess what they represented. Voila, rotating daily passwords that are
different from year to year.
dixie
<ji********@compumarc.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com... dixie wrote:.. I also used Left$ and Right$ on them so that if anyone ever finds the table, it still wont give them the password. The only other thing I will look at here is that at the end of the year, to somehow scramble the passwords so the passwords for next year are different for the same day than they were this year.
Thats's a very clever idea, Dixie. You could keep the same passwords the next year and vary whether Right or Left is used and vary how many characters are used. Mid(s) would really mess with their minds :-). James A. Fortune
Well actually, using the 1st number of the year would be stupid as it is
going to be a 2 for the next 995 years :-)
dixie
"dixie" <di***@dogmail.com> wrote in message
news:42********@duster.adelaide.on.net... Actually, just concatenating the 1st and last digits of the year into the password somewhere would work. Mine already have numbers in then, so nobody would guess what they represented. Voila, rotating daily passwords that are different from year to year.
dixie
<ji********@compumarc.com> wrote in message news:11**********************@o13g2000cwo.googlegr oups.com... dixie wrote:.. I also used Left$ and Right$ on them so that if anyone ever finds the table, it still wont give them the password. The only other thing I will look at here is that at the end of the year, to somehow scramble the passwords so the passwords for next year are different for the same day than they were this year.
Thats's a very clever idea, Dixie. You could keep the same passwords the next year and vary whether Right or Left is used and vary how many characters are used. Mid(s) would really mess with their minds :-). James A. Fortune
dixie wrote: Actually, just concatenating the 1st and last digits of the year into
the password somewhere would work. Mine already have numbers in then, so
nobody would guess what they represented. Voila, rotating daily passwords
that are different from year to year.
dixie
Thank you for your helpful ideas also. BTW, bean239 is from a dumb St.
Patrick's Day joke. Why don't Irishmen eat more that 239 beans on St.
Patrick's day? Too farty (groan).
JAF
Prehaps i am missing something, but what is the point of having a
rotating password? How does the user know what password to use, or
remember all of them? If it is an installer/licensing solution, you
can't just scramble all 366 passwords around every year - you as the
auther also need to know which password to use.
Nicolas
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Thankyou James, you are too kind. I often have what I consider are good
ideas, but often lack the programming skill to put them into code. I am
slowly learning though and this news group has been a terrific help to my
tardy development.
dixie
<ji********@compumarc.com> wrote in message
news:11**********************@c13g2000cwb.googlegr oups.com... Dixie,
You certainly are creative. Feel free to share any innovations you have with the rest of us. Often users are not sophisticated or will be fired if they tamper with things they shouldn't so the company doesn't mind a little 'openness' in the implementation. Security to prevent employees from getting at things and security to prevent hackers from getting at things are different ballgames. I need to use less cliches. Washington would cease to function without them.
James A. Fortune This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Max |
last post by:
Hi,
What is the best way to change passwords via php?
I was first thinking of using the chpasswd function, but even though I added
an entry for apache to be able to run chpassword vi visudo,...
|
by: Lim Eng Teik |
last post by:
I was asked by a client to make changes for their Outlook Web Access page
where I need to validate Expiry Date of the Password and also the Password
Length for the NT Account Policy. Initially I...
|
by: Joseph Braganza |
last post by:
I have forgotten my administration password on XP.
Is there any solution?
|
by: Ben Allen |
last post by:
Hi,
I want to create a password protected page to administer my site from
(the news is read from a mySQL database and I have created a PHP form to
as a GUI to do this). I thought of...
|
by: isaacrajan |
last post by:
Hello,
Is there a way in which users can be prevented from making changes to
regional settings in Win XP Professional edition so that the
interpretation of dates by an Access application remains...
| |
by: Colleyville Alan |
last post by:
I have some data in a table structured like this:
Date Cust_ID CUSIP Amount
01/31/2005 060208 02507M303 27,061.84...
|
by: Drew Pawlik |
last post by:
I am needing to write an application that will be used every month to
automatically run queries on an Oracle database. But the password I need to
log in to the database needs to be changed every...
|
by: Zeba |
last post by:
Hi,
I have a page with a calendar and two datalist items - one containing
month values and the other, year values. Depending on the month/year
value chosen ( in text/string format ) I should be...
|
by: =?Utf-8?B?QXhlbCBEYWhtZW4=?= |
last post by:
Hi,
we've got a strange problem here:
We've created an ASP.NET 2.0 web application using Membership.ValidateUser()
to manually authenticate users with our website.
The problem is: If the...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
| |
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated ...
| |
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| |