A very strong suggestion:
Do not have the Primary Key be some kind of compound number and text like "LAP001". Make it a rule to use an abstract primary key, an autonumber, in all situations unless there is a pressing and proven business requirement to use something else. I'd suggest something like the following:
tblDevice
DeviceID Autonumber Primary Key
DeviceSerialNumber Text(50) Unique Required
DeviceTypeID Long (Foreign Key to tblDeviceType) Required
DeviceDatePurchased DateTime
etc
tblDeviceType
DeviceTypeID Autonumber Primary Key
DeviceType Text(50) -- joins to tblDevice
tblUser
UserID Autonumber Primary Key
UserName Text(50)
etc
tblDeviceUserHistory
DeviceID Primary Key, Foreign Key (to tblDevice) -- Or use an abstract key just for this table, if that will prove simpler than a compound key
UserID Primary Key Foreign Key (to tblUser) -- ditto
DateUsedFrom DateTime Required -- You might consider a unique index that combine DeviceID, UserID, DateUsedFrom if you envisage issueing the same device to the same user more than once
Notes Memo
etc
Trust me on this. It's what I do for a living, design databases, and this is based on years of fixing other people's bad designs! How are they "bad"? They force the business to fit the database, not have the database assist the business.