Not sure I understand what you mean by a big list and a small list.  When
they drop off that small list, what happens?  They can no longer login?  If
so, what good does it do to keep them in the big list?

In short, what are you really trying to accomplish here?  Do you want weekly
password expirations?  Do you want them to have to get reset by the
administrator every 7 days?  What's the goal?

Access has very good built-in security.  I always try to discourage people
from trying to reinvent the wheel.  I see lots of posts on here about
securing just one form with a password, or tying passwords to switchboards,
etc.  I have about 40 users on a large database using Access built-in
security and am able to restrict it as loosly or as tightly as I need to by
limiting their access to objects or writing code that is based on the User
Group to which they belong.

You told us how you are attempting to solve your issue, but you never told
us the issue.

Rick B

Just new to access and asp and would like to know if an idea I have would
work.

What I'd like to do is set up a sign in / password / one week to access
time.

Here's what I was thinking. I don't know if it's possible or not, nor do I
know what such a thing would be called to be able to look it up in the help
section or one of the books I have here.

What I would like is to have a main table with user info. Then I would like
smaller tables derived from the big table but the users would only be on it
for 1 week after the first time he/she signed in.

I was thinking this could maybe be done in access with some sort of rule or
something. The first time a user acesses the account, the main table is
updated to the current date. I believe I can do this with asp when we sign
them up.  Then the user's name and password automatically becomes part of
the smaller table. After 1 week though, the user stays on the main big table
but is dropped off the smaller list.

Ideas, suggestion, possible solutions welcome. thanks.

If I understand what you are saying here it sounds like
something straight forward.  In your Users table you might
have fields like UserId, UserName, UserPW, LogInDate etc.  
Then you can create a form and have the users login and
you can update the LogInDate and/or test the LogInDate to
the current date to take a particular action.