C
Christina
I am a fairly new Access user and am having trouble
setting up my database most efficiently.
I have a large group of signs, each with individual
physical attributes. I would like to have one table with
the sign name as one field and the physical attributes as
others (ie, height, width, color, etc). Then I would like
to have another table that computes the sign design
criteria based on the physical attributes listed in the
first table. I need it to run like this, I enter the sign
name into a form, then Access retrieves the physical
attributes from the sign table and uses them to perform
the calculations as appropriate.
I currently have just one table/form and all of the sign
attributes are listed in if then statesments in code (ie
if SignDesignation = "1a" then width=24). This worked
fine for a while, but now I have too many signs, and the
code has become too large access errors out.
I have also tried breaking that portion of the code into
several smaller procedures and was hoping to call each
procedure using a macro, but I am having trouble getting
that to work too.
Ideally I would like to have two seperate tables. I think
I should be able to do this using relationships, but
haven't been able to get it to retrieve the physical
aspects. Any ideas?
setting up my database most efficiently.
I have a large group of signs, each with individual
physical attributes. I would like to have one table with
the sign name as one field and the physical attributes as
others (ie, height, width, color, etc). Then I would like
to have another table that computes the sign design
criteria based on the physical attributes listed in the
first table. I need it to run like this, I enter the sign
name into a form, then Access retrieves the physical
attributes from the sign table and uses them to perform
the calculations as appropriate.
I currently have just one table/form and all of the sign
attributes are listed in if then statesments in code (ie
if SignDesignation = "1a" then width=24). This worked
fine for a while, but now I have too many signs, and the
code has become too large access errors out.
I have also tried breaking that portion of the code into
several smaller procedures and was hoping to call each
procedure using a macro, but I am having trouble getting
that to work too.
Ideally I would like to have two seperate tables. I think
I should be able to do this using relationships, but
haven't been able to get it to retrieve the physical
aspects. Any ideas?