PC booking system

need help designing a database for PC booking system ? I have 3 labs and students should be able to book a PC 1 week or even 1 Day before if they want to work extra. Database should store student Login time and info. (Well this is some programming technique) but I need to have some fields so that data should be dumped into database so as to keep a record if the student has consumed his/her time or not.

Very Urgent a quick response will be highly appreciated.From that informaiton, I would reccomend three tables, (Labs, Students, and schedule) Possible design:

Labs
Labname
Location
...

Students
StudentPK
Firstname
Lastname
...

Schedule
ScheduleID
Labname
StudentPK
Date
Logintime
Logouttime
...

Probably more you could do but this should get you started, researching normalizaiton should help as well.

HTHsql

Password protection

Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Password protection

Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".
Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>
|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Password protection

Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.