I'd think you might want to have a Chemicals table, and just reference that
from the log, just so references to the same chemical would be consistent.
Use a ComboBox with the Chemicals table as its Row Source and bind it to the
Chemical ID field in the log so the user can select the chemical... the
Chemicals table would contain, at least, ChemicalID and ChemicalName, but
could well contain other information about the chemical itself.
_I_ would think Access 95 was a problem. It was, arguably, the buggiest
release of Access ever... never had even one Service Pack to fix the bugs,
and everyone who seemed to know much about Access ditched it as soon as they
got their hands on Access 97... but even Access 2000 ("the Work of Art",
according to some) is out of support. I wouldn't start an important new
project with a product that was never that great and several years out of
support, with not even security patches being created for it. I'd consider,
perhaps, whether to choose Access 2002 or Access 2003 for new work.
Larry Linson
Microsoft Access MVP
pdruff said:
I just started working in a place that has used an access database to log
in all materials for the last 4+ years (chemical names, storage locations,
hazards, other information). They manually decide what to enter in 8-10
different fields. is there a way that they could enter in the chemical name
and have it populate the fields based on the way that they were entered in
the last time? just trying to come up with a way to help it get done the
same way every time. The other thing is they are still using access 95,
is that a potential problem?
