J
Jim
Years ago I did a little work on several Access data bases, for my own
use, but that was the end of it and I quickly forgot everything that I
knew - which was little.
Now I'm about to start again to try and make a data base that will be
used to index information from my own library of aviation material.
Just as a bit of background I have about 50,000 records hand written on
5x8 file cards which probably cannot be transcribed into a new data base
as the criteria has developed and changed over the years - so be it.
Also I have some 28,000 records in an incomplete [read still under
development when the plug was pulled] Paradox data base. I've managed
to convert those files to Access but again the format has changed so
much that I probably cannot move them to any new Access data base that I
may develop.
Ok, so much for the sob story. What I would like is for someone to
look at this and say yes or no as to the way to go.
I'll have a Combo Box with the various manufacturers listed and to be
entered in the data base. With the selection of a specific manufacturer
I'll be wanting to activate another Combo Box with a list of the
aircraft produced by that manufacturer so that I can control the type
and name entry information - that is keep it all the same. This is
especially true for WW2 Japanese manufacturers with both a short and a
long identification for the same aircraft, a Type number, a Japanese
name, a translation of that name and the assigned Allied code name. It
tends to get pretty heavy and I'd like to work with the Combo Box as the
number/letter combinations and spellings can become complicated if
trying to type them in often without the complete data available at the
source of reference.
As I see it I'll have to develop a secondary Combo Box for each and
every manufacturer. So far I have over 1200 manufacturers listed with
hundreds more waiting in the wings. Will Access handle something like
that or is there a better way to go? If yes, I'll start working on it
and probably return here for some advice.
Thank you. cheers - Jim.
use, but that was the end of it and I quickly forgot everything that I
knew - which was little.
Now I'm about to start again to try and make a data base that will be
used to index information from my own library of aviation material.
Just as a bit of background I have about 50,000 records hand written on
5x8 file cards which probably cannot be transcribed into a new data base
as the criteria has developed and changed over the years - so be it.
Also I have some 28,000 records in an incomplete [read still under
development when the plug was pulled] Paradox data base. I've managed
to convert those files to Access but again the format has changed so
much that I probably cannot move them to any new Access data base that I
may develop.
Ok, so much for the sob story. What I would like is for someone to
look at this and say yes or no as to the way to go.
I'll have a Combo Box with the various manufacturers listed and to be
entered in the data base. With the selection of a specific manufacturer
I'll be wanting to activate another Combo Box with a list of the
aircraft produced by that manufacturer so that I can control the type
and name entry information - that is keep it all the same. This is
especially true for WW2 Japanese manufacturers with both a short and a
long identification for the same aircraft, a Type number, a Japanese
name, a translation of that name and the assigned Allied code name. It
tends to get pretty heavy and I'd like to work with the Combo Box as the
number/letter combinations and spellings can become complicated if
trying to type them in often without the complete data available at the
source of reference.
As I see it I'll have to develop a secondary Combo Box for each and
every manufacturer. So far I have over 1200 manufacturers listed with
hundreds more waiting in the wings. Will Access handle something like
that or is there a better way to go? If yes, I'll start working on it
and probably return here for some advice.
Thank you. cheers - Jim.
Thank you for the information and the