Background:
I use a few related databases in Filemaker Pro 6 (our school district
has now licensed 8 but we are not upgraded yet) to manage nearly all
facets of our choral music program. I "stole" the original DB from a
colleague and have since added to it significantly.

The main file contains student info, scheduling (related to main
teacher db & course db), accounting, miscellaneous notes, and wardrobe
items checked out (related to Wardrobe master database).

Each record in the wardrobe DB is one item of inventory - a dress, tux
jacket, shirt, etc. Most of the items are new in the last year or two
and so I would like to keep a complete record of the history of each
item.

As they will be checked in I would like to add a record of who used
it, when, what condition it was in. I created a repeating field but
that seems like it is going to be a nightmare to update using my Check-
In script.

Any suggestions for going about tracking checkout history?

"B. Monse" <brmonse (AT) gmail (DOT) com> schreef in bericht
news:1180027445.136128.137600 (AT) h2g2000hsg (DOT) googlegroups.com...
Keep away from repetitions here! In my opinion a new table is in place here.
a join between the student (who might use any number of items any number of
times) and a clothing item (that might be used by any number of students any
number of times) so you have a many2many here. As a basis for the new table
you will start off with a few fields here.
Student_ID
Wardrobe_ID
Out_Date
In_Date
Every time a student comes in to use a wardrobe item, you create a new
record in this table. Store student_id, wardrobe_id and out_date. When the
student returns the item store in_date.
This can all easily be tracked through portals, or calculations. Whatever
you need.

Hope this will get you on your way

keep well. Ursus