Archiving Entries

[Brian Mosher]

I have a very simple form in Access 2000 that a user can enter information
about IV Pumps and keep track of them. They enter the patient, facility,
serial #, date it went out, date it came in, date it needs to be serviced,
etc. We have to keep a running history of that dates it came back to us, and
went out to a patient though. Can anyone think of a simple way that each time
they enter a date in these 2 fields, it could be kept in another table, and
referred back to as necessary? So when they go to the record in the form, it
would show the most recent entries, but they could click on something to
allow them to see what dates it has been checked in and out in the past. It
seems really simple in theory, and I'm sure it's easy to accomplish, but it's
been years since I've done any sort of developing in Access. The ideas are
not coming to me.

Thanks,

Brian Mosher

 

[KARL DEWEY]

You need to tables - IV Pump, Issue_Return, and PumpMaint.
IV Pump ---
PumpID - autonumber - primary key
serial - text
Model - text
DateInSvc - DateTime

Issue_Return ---
IssueID - autonumber - primary key
PumpID - number - integer - foreign key
Patient - text
Facility - text
DateOut - DateTime
DateIn - DateTime
Remarks - text or memo

PumpMaint ---
MaintID - autonumber - primary key
PumpID - number - integer - foreign key
Type - text - repair, calibration, etc.
MaintDate - DateTime
Remarks - text or memo

Use form/subform for pump/issue and pump/maint. The query for the issue to
pull records without a DateIn. Form maint subform on open goto last record
sorted in date order.

 

[KARL DEWEY]

a pump can be simultaneously in the maintenance shop and 'issued' to a
patient
I see your point so reduce the number of tables.
Issue_Return ---
IssueID - autonumber - primary key
PumpID - number - integer - foreign key
Action - text - issue, repair, calibration, etc.
OutTo - text
DateOut - DateTime
DateIn - DateTime
Remarks - text or memo

multi-million USD indemnity insurance cover.
Why did you not impart some of your wisdom in answering the individual’s
inquiry?

 

[Brian Mosher]

Yea, this is truly a simple database to keep track of where our pumps are.
This has absolutely nothing to do with dispensing. Our dispensing system is a
completely separate program that I have nothing to do with. This is a network
admin telling someone "I'll put a database together for you to take place of
this tiny insignificant module in an old system we aren't using anymore and
are decomissioning". The only thing we HAVE to be able to show is the dates
they were issued and returned. And tecnically they could keep up with this on
paper. We only have about 70 pumps. Just trying to make it as simple as
possible for them. No "life-critical system" here, no "complex data model".
Hence my thought to ask this simple question on a message board.

I've played around with the 2nd table a little bit, but can't get it to
quite work the way i want. I'll get it to work sooner or later.