Asset Management

  • Thread starter Thread starter Daniel
  • Start date Start date
D

Daniel

Hi,

I am developing an Asset Management system. The
requirement is that for a specific asset, there are 2
employees (Can be the same), one is the owner and the
other is for maintenance.

Should I create a table named "Asset Staff" with the
following items:
1) AssetStaff ID
2) Asset ID
3) Staff ID
4) Owner - Yes / No - Yes for Owner and No for
Maintenance ?

Your advice is sought.
 
Great little question!!!

Perhaps you could move out the "owner" to a combo box on the "main" form
that lets you select ONE persons from the "asset staff" table. (it would
store the value to a new column you make called OwerID).

And, you also would create a maintains combo box (and MaintaqnceID field)
for the maintains.

It would then be impossible for a end user to select more then "one" person
as the owner, and of course this would also save a lot of messy code to
"test" for this fact. Further, I think writing reports would be a bit
easier. And, perhaps down the road, you might have additional owners..but
want to keep the previous owner there for history reasons. You could enter
some extra notes in a description column you add to this "asset staff
table". With a with a yes/no field you can't do stuff like this without
chaining your design. And, since there is ONE owner only, then having a
field that stores this owner in the main record would better represent hits
fact then having a repeating yes/no field. On the other hand, if you need
multiple owners..then you would repeat the yes/no field as you have...
 
Daniel said:
I am developing an Asset Management system. The
requirement is that for a specific asset, there are 2
employees (Can be the same), one is the owner and the
other is for maintenance.

Should I create a table named "Asset Staff" with the
following items:
1) AssetStaff ID
2) Asset ID
3) Staff ID
4) Owner - Yes / No - Yes for Owner and No for
Maintenance ?

Simply:

Asset_ID, Owner_Staff_ID, Maintainer_Staff_ID

makes a lot of sense to me.

Jamie.

--
 
Hi,

All you need is:

1) AssetStaff ID - table autonumber key
2) Asset ID - link to key in asset table
3) Staff ID - link to key in employee
4) Owner ID - link to key in employee table

If the staff and owner are the same you'll just have 2 fields with the same
field value. Your tables will still be normalized and should work fine.

Frank Stepanski
 
Frank said:
All you need is:

1) AssetStaff ID - table autonumber key
2) Asset ID - link to key in asset table
3) Staff ID - link to key in employee
4) Owner ID - link to key in employee table

I disagree: your item 1 is strictly optional. In fact, there's no
reason why your items 3 and 4, being attributes of an asset, can't in
the Assets table.

Jamie.

--
 
Back
Top