Tracking Software on Workstations

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I'm having trouble creating a db that would allow me to track software on
employees workstations. I can't seem to link the Products table to the
Workstations table. Below are tables and fields that I've created. The ones
in caps are primary keys.

Workstation: WORKSTATION_ID(number), DepartmentID(text), EmployeeID(text)

Products:PRODUCTID(autonumber), ProductName(text), Manufacturer(text),
Version(text), Category(text), LicenseID(text)

Employees: EMPLOYEEID(text), FName(text), LName(text), DepartmentID(text)

License Agreements: LICENSEID(text), Manufacturer(text), ProductName(text),
NumberofUnits(number), Cost(currency), Expiration(date/time)

A workstation can have many products and a product can exist on many
workstations. Is this the correct of creating this db with all the tables
I've created? I don't know how to link the Products table with the
Workstations table. I thought maybe I need to create another table called
Installations with the following fields: WORKSTATION(number) and
PRODUCTID(text), but it's not working properly.

I hope someone can help or suggest a better way of doing it.

Thanks in advance!
bagia
 
A workstation can have many products and a product can exist on many
workstations.
Click to expand...

In that case, you need a new table called Licenses, containing foreign keys
referencing the Workstations table and the Products table. There may be
other fields needed, like

Licenses( *WorkStationID, *ProductID, InstalledBy, InstalledDate,
IsOwnedByCompanyOrEmployee, HasManagementApproval, VersionNumber, etc etc)

It's common to make the Primary Key out of the two foreign keys, so that
the same product can only exist once on each workstation.

Hope that helps



Tim F
 
Tim,

So when I link the tables together, (*WorkstationID) would link to
(*WorkstationID) field in Workstation table? I created a table called
Installations with 2 foreign keys as primary key, but when I linked the
tables together it tells me that there's mismatch data.

Would it work if I create a table called Installations with the following
fields?
*Autonumber, WorkstationID, ProductID

Is there anyway I can send you the db that I've created so that you can see
exactly what I did?

Thanks for your help Tim
 
Make sure that you use the data type number for WorkstationID and ProductID
in your Installations Table. The data type needs to be the same. If you
have set up workstationID and productID as something other than autonumber in
the original tables, then just make sure that when you use them as foreign
keys they are set to the same data type.
 
Back
Top