Re: Solution Required

Dear Lee:
The learning never stops.
Lets start with this:
What do you think the relationships should be?

I am willing to help, but not do it for you. :o)

Lee Osborne <osbornelee_at_hotmail.com> wrote in message news:989499812.29494.0.nnrp-07.c2de1f0e_at_news.demon.co.uk...
> Hi all,
>
> I'm designing a database model for my first SQL web database project. I
 have
> read as much about this as I can but have no more time to learn more.
>
> Project.
> --------
>
> On-line password protected database. Authorised users can login via a
 login
> screen in the browser. This then gives them a list of menu options that
> allow the user to view certain features/areas.
>
> Requirements.
> --------------
>
> . 5+ levels of user access with several freely assignable features/areas
> available according to the user's assigned access level.
>
> . Users can be searched by various columns which again are freely
 definable
>
> . Users have the usual fields, but have a choice of several company
> division, the choice of access level and a choice of country of residence.
>
>
> Notes.
> -------
>
> . The access levels are freely assignable and can be modified.
>
> . The features/areas can be freely assignable to the relevant access level
> and can be modified.
>
>
>
> I have created the following tables:
>
> userTbl
> accessLevelTbl
> countryTbl
> divisionTbl
> featureTbl
>
> Each table has a ID field as the primary key.
>
> Will this model be ok or are there any problems? What relationships do I
> need to consider?
>
> Any help will be much appreciated,
>
> Thanks
>
> Lee.
>
>
>
Received on Sat May 12 2001 - 06:44:32 CEST