J
Jim Ory
Using WinXP & Access2K2
In my database board members are coded as President, Vice-President,
Secretary, and so on. There are a total of 7 positions.
Two tables take care of this, one table for the "entity" and one table for
the "position". An "Add/Edit" form for the Entities and a subform for the
Positions handles the data. Each year, one or more of these entities become
board members, non-board members, or they change board positions. As these
changes are being entered into the database, there is a strong possibility
that adding or changing a position of an entity will cause duplicate
positions.
I would like to add code in an event that would check for duplicate
positions before allowing the data entering person to proceed. If there are
duplicate positions, give them a message box telling them what the problem is
and how to remedy the duplicate entries.
In the after update event, I put code to run a "Find Duplicates" query. It
is quite crude and would require that I train all data entry persons what to
do with the query after it has run. It is fine for me, but not so elegant and
simple for others.
Thanks in advance.
In my database board members are coded as President, Vice-President,
Secretary, and so on. There are a total of 7 positions.
Two tables take care of this, one table for the "entity" and one table for
the "position". An "Add/Edit" form for the Entities and a subform for the
Positions handles the data. Each year, one or more of these entities become
board members, non-board members, or they change board positions. As these
changes are being entered into the database, there is a strong possibility
that adding or changing a position of an entity will cause duplicate
positions.
I would like to add code in an event that would check for duplicate
positions before allowing the data entering person to proceed. If there are
duplicate positions, give them a message box telling them what the problem is
and how to remedy the duplicate entries.
In the after update event, I put code to run a "Find Duplicates" query. It
is quite crude and would require that I train all data entry persons what to
do with the query after it has run. It is fine for me, but not so elegant and
simple for others.
Thanks in advance.