Originally Posted by
Ajax
you need to describe the relationship between members and assets.
As described from your table design, many members can have the same asset at the same - and only one asset.
think you need a joining table and lose the fldAsset in the member table
tblMemberAssets
MemberAssetPK
MemberFK
AssetFK
DateLoaned
DateReturned
you may need rules to ensure an asset cannot be loaned out if already on loan - indicated by using something like Dcount("*","tblMemberAssets","DateReturned is null AND AssetFK=" & me.assetFK)>0 on a form
and perhaps members cannot borrow more than one asset at a time - indicated with something like indicated by something like Dcount("*","tblMemberAssets","DateReturned is null AND MemberFK=" & me.MemberFK)>0