What if the seating chart were a database where each seat was a record and each seat was filled by a student value in that record. Then on the layout you display, graphically or whatever you need, each seat it¹s associated student. You could even use one seating database for all seating charts by making each record uniquely indicating the class/semester whatever. I would use a separate seating database for each room though just to alleviate confusion. This would also lend you historical records of who was assigned to each seat for the life of the database.
Interestingly, you could do some trend analysis on the students if you get enough data where do they sit and how does that affect performance. The common belief is that there is a correlation but I didn¹t always sit in the front row :) Sable On 4/19/07 9:29 AM, "Bill Walllace" <[EMAIL PROTECTED]> wrote: > I have struggled from about a week trying to link a seating chart to a student > database. The problem I keep coming back to is that the seating chart has only > one record and so a normal relationship does not work. I tried using multiple > fields for each student on the map but that did not seem to work either. There > must be some easier way to accomplish this task. > > Thanks for any suggestions, > > > > > > Bill Wallace > > Librarian > > Manzano Day School > > Albuquerque, NM 87104 > > School email - [EMAIL PROTECTED] > > > >
