Database design for ID Card

[Randy Hartwick]

I have a database designed to maintain Firearms Permit
information. The main table has information about the
applicant and has approximately 70 fields. A second table
has information on firearms owned and contains 15 fields
for each firearm. The second table is related to the main
table in a one-to-many relationship.

I need to create an ID card that will print the applicant
information on the front of the card and list each firearm
owned on the back of the card.

My problem is that all of the ID Card creation software
that I have found will not handle data from a one-to-many
relationship. All of them require that all information
printed on a single card be contained in a single record.

My questions:

1. Does anyone know of existing ID Card Software that will
handle a one-to-many relationship and will work with a
Fargo HDP ID Card Printer.

2. Is there a way that I can extract the data from the
relevant fields of the main table (18 fields) and the data
from relevant fields of the second table (5 fields for
each firearm owned - potentially 15+) and place all of
this information in a single record. (I have been
thinking an array might work but am unsure of how to do
this in MS Access).

Thanks for any help.

 

[Pavel Romashkin]

Being utterly unfamiliar with "ID card software", I am thinking that you
want to print out, on a double-side capable printer, a paper document
that has applicant info on one side and his firearms list on the other.
Am I right?
If not, please ignore the rest of this post. You may be speaking about
plastic ID cards, which will be printed using special hardware and software.
If yes, you can simply create an Access report, which will do what you
want. You can include personal information in the mail part of the
report, and create a subreport that will list the firearms.

Pavel

 

[John Nurick]

Hi Randy,

Your (2) can certainly be done. The best way will depend on the layout
that the ID card software wants the data in, but assuming it wants 18
fields for the person and 5 fields for as many guns as will fit on the
card - 5 or 10 I guess - it should just need a cunning query or three.

I suggest you post again in the Queries newsgroup
(microsoft.public.access.queries) where the real experts hang out,
giving more information about what the ID card software needs and the
names of the more important fields.