transferring info at the click of a button!

capn beanfart

New member
Local time
Today, 15:41
Joined
Jul 15, 2003
Messages
9
Hi there everyone...

I'm creating a database for an equipment sign out system in a college.

At the moment, I have a form to type in the students details, equipment borrowed and date due back.

When the student brings equipment back, I can bring up their details by searching for their name using a query.

I have a tick box titled 'returned' on the form. This would probably be better as a command button actually..

I need these students info to be stored in another table and deleted from the 'current' loaned equipment list when this tick box is clicked, as it is no longer necessary to store it there.

I know how to activate a macro using the on click option, but not how to transfer then delete the file.

Help!

Cheers

Phil
 
Phil,

Moving all of that data around makes things more
difficult for you.

tblLoans:
LoanID - Autonumber
StudentID
LoanDate
ReturnDate

tblLoanItems:
LoanID
ItemID
Quantity

tblStudentInfo:
StudentID
OtherInfo ...

TableStructures like the above will let you simply put in
a return date when the items are returned. At any time
your outstanding items are the ones without return dates.

If you put the return date on the tblLoanItems, you can
account for the times where they borrow 5 items yet return
only 4.

Wayne
 
Hi Wayne...

Thanks for responding so quickly. At the moment, when the equipment is returned I click the yes/no box. This ables me to identify whether the equipment has been returned or not when looking through/searching the table.

The problem with having returned and non-returned information in the same table is that when I search for an item of equipment (eg: 'PENTAX') to find out where it is, I want it to bring up results from currently loaned equipment, NOT returned equipment as this just confuses matters...

This is why being able to transfer the info to a separate table would be really useful (we need to keep what people have borrowed on record in case we find fault with it and need to give them a call, otherwise I would say delete it!)

Hope this makes sense!

Phil
 
Why not use a query for that, requesting those records where returned = not checked (false)

From a design point off view this would be the better sollution. Unless your dealing with millions of loans a month but then i would atleast go for a SQL server backend ;)

Regards
 

Users who are viewing this thread

Back
Top Bottom