Database Design

Hi all,

I need some advice with a database I’m trying to design. Its main purpose is
to asset track PC’s and other related items within several different project
areas i.e. the item e.g. a monitor may move from one project into another
(the monitor itself has its own unique reference number). The project is
“owned� by an individual which subsequently each item has a current owner
assigned to it. I have designed 4 main tables:

1) TblGeneral - This hold all the data of the item itself i.e. unique
number, Serial Number, Owner, Specification, Processor etc..
2) TblSoftware – This holds the data on software which is linked as a one-to-
many relationship with the MAC Address within the TblGeneral.
3) TblRemovable Hard Disks – Computers in some instance may have multiple
removable hard disks. This is linked as a one-to-many relationship with
Computer Inventory number
4) TblMonitor- Each computer may have multiple monitors. This is also linked
as a one-to-many relationship with the computer Inventory Number

I want to create a login whereby a owner can login and through a series of
forms and queries, be able to view there individual items.
Can you tell me of any good resources I can look at to enable me to does this?

I do not have any knowledge of SQL but am wishing to learn.

--
Message posted via http://www.accessmonster.com

Explorers were cutting through the deep, dark jungle. Suddenly they heard
drums off in the distance. Their native guide yelled “Run. We must get out of
here before the drums stop.� The explorers asked why and the guide said
“That’s when the bass solo starts.�

Sorry but when I saw your user name, I couldn't resist.

I think that your table structure is wrong. You should not have seperate
tables for monitors, software, etc. Rather you should have a table of Owners;
another table of Objects; and a table of Projects.

The Objects table would be linked to the Projects table and hold records for
all the objects used in that project such as monitors, software, etc. I'm
assuming that an Owner could have more than one Project. Therefore the
OwnerID would be the link to the Projects table.

Then an Owner could find out what they own and under which project.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

"Bass_Player via AccessMonster.com" wrote:

Hi all,

I need some advice with a database I’m trying to design. Its main purpose is
to asset track PC’s and other related items within several different project
areas i.e. the item e.g. a monitor may move from one project into another
(the monitor itself has its own unique reference number). The project is
“owned� by an individual which subsequently each item has a current owner
assigned to it. I have designed 4 main tables:

1) TblGeneral - This hold all the data of the item itself i.e. unique
number, Serial Number, Owner, Specification, Processor etc..
2) TblSoftware – This holds the data on software which is linked as a one-to-
many relationship with the MAC Address within the TblGeneral.
3) TblRemovable Hard Disks – Computers in some instance may have multiple
removable hard disks. This is linked as a one-to-many relationship with
Computer Inventory number
4) TblMonitor- Each computer may have multiple monitors. This is also linked
as a one-to-many relationship with the computer Inventory Number

I want to create a login whereby a owner can login and through a series of
forms and queries, be able to view there individual items.
Can you tell me of any good resources I can look at to enable me to does this?

I do not have any knowledge of SQL but am wishing to learn.

--
Message posted via http://www.accessmonster.com

LOL!!!

Thanks Jerry. I am trying to find a good resource whereby I can learn SQL,
do you know of any good books I can buy?? (I am a complete novice)

Jerry Whittle wrote:
Explorers were cutting through the deep, dark jungle. Suddenly they heard
drums off in the distance. Their native guide yelled “Run. We must get out of
here before the drums stop.� The explorers asked why and the guide said
“That’s when the bass solo starts.�

Sorry but when I saw your user name, I couldn't resist.

I think that your table structure is wrong. You should not have seperate
tables for monitors, software, etc. Rather you should have a table of Owners;
another table of Objects; and a table of Projects.

The Objects table would be linked to the Projects table and hold records for
all the objects used in that project such as monitors, software, etc. I'm
assuming that an Owner could have more than one Project. Therefore the
OwnerID would be the link to the Projects table.

Then an Owner could find out what they own and under which project.
Hi all,

[quoted text clipped - 20 lines]

I do not have any knowledge of SQL but am wishing to learn.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200704/1

On Sun, 22 Apr 2007 18:34:56 GMT, "Bass_Player via AccessMonster.com"
u33455@uwe wrote:

Thanks Jerry. I am trying to find a good resource whereby I can learn SQL,
do you know of any good books I can buy?? (I am a complete novice)

Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/acc...resources.html

The Access Web resources page:
http://www.mvps.org/access/resources/index.html

John W. Vinson [MVP]

Before learning SQL, I highly suggest getting some relational database
training or reading "Database Design for Mere Mortals" by Hernandez first.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"Bass_Player via AccessMonster.com" wrote:

LOL!!!

Thanks Jerry. I am trying to find a good resource whereby I can learn SQL,
do you know of any good books I can buy?? (I am a complete novice)

Jerry Whittle wrote:
Explorers were cutting through the deep, dark jungle. Suddenly they heard
drums off in the distance. Their native guide yelled “Run. We must get out of
here before the drums stop.� The explorers asked why and the guide said
“That’s when the bass solo starts.�

Sorry but when I saw your user name, I couldn't resist.

I think that your table structure is wrong. You should not have seperate
tables for monitors, software, etc. Rather you should have a table of Owners;
another table of Objects; and a table of Projects.

The Objects table would be linked to the Projects table and hold records for
all the objects used in that project such as monitors, software, etc. I'm
assuming that an Owner could have more than one Project. Therefore the
OwnerID would be the link to the Projects table.

Then an Owner could find out what they own and under which project.
Hi all,

[quoted text clipped - 20 lines]

I do not have any knowledge of SQL but am wishing to learn.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200704/1