i don't need to see your data, just the empty shell with relationships. Please!

There's very little to see. A Users table with UserName (unique, non-null)
and Password (non-null). If you don't use roles in your app, that's
basically it, though obviously you may wish to store other user information
specific to your app.

If you do use roles in your app, you'll also need a Roles table and a
linking RolesUsers table to implement the many-to-many relationship between
Roles and Users. Relationships are one User to many RolesUsers, and one Role
to many RolesUsers, i.e. one User may be a member of many roles, and one
role includes many users.

If you have access (no pun intended) to VS.NET and SQL Server (MSDE will do)
take a look at Microsoft's ASP.NET Portal Starter Kit ...

http://www.asp.net/StarterKits/DownloadPortal.aspx

It uses a SQL Server database, but that's an implementation detail, the
design is the same. The relevant tables in that database are Portal_Users,
Portal_Roles, and Portal_UserRoles.

--
Brendan Reynolds
Access MVP

"Annetty" <(E-Mail Removed)> wrote in message
news:75B43A6D-E33D-4B33-9A9C-(E-Mail Removed)...
>i don't need to see your data, just the empty shell with relationships.
>Please!