How do I link a record to a column in another table?

[PaulNaude]

I would like to know if it is possible to link records in one table to
columns in another with standard db design (i.e. without coding the addition
or removal of a column when the applicable record in the table is deleted).

I do not want to use a many to many relationship for this specific example
in order to simplifly the procedure for the user:

I Have equipment and each type has applicable parameters. If the user add a
new parameter to the list of paramereters, he has to select in another table
to which types of equipment this parameter applies.
I.e., in the list of equipment types, there should be YES/NO columns for
each parameter from where to choose wheteher it is apllicable or not.
So, if the list of parameters change, so must the columns in this table.

It will be easy by forcing the user to use a form for the deletion and
addition of parameters (where underlying code can then do the rest) but since
I will be accessing the database from another program (VB.NET application), I
would like to the design the db in such a way that I do not need a form to
make the neccesary changes (or would it be possible to use the db's form in
my application in such a way that it seems part of my application?)

Any ideas?

 

[John Nurick]

I would like to know if it is possible to link records in one table to
columns in another with standard db design (i.e. without coding the addition
or removal of a column when the applicable record in the table is deleted).

It's not possible.

I do not want to use a many to many relationship for this specific example
in order to simplifly the procedure for the user:

Like it or not this *is* a many to many relationship between equipment
types and parameters.

I Have equipment and each type has applicable parameters. If the user add a
new parameter to the list of paramereters, he has to select in another table
to which types of equipment this parameter applies.
I.e., in the list of equipment types, there should be YES/NO columns for
each parameter from where to choose wheteher it is apllicable or not.
So, if the list of parameters change, so must the columns in this table.

It's highly undesirable and never or virtually never to alter the design
of tables as part of ordinary database operations.

It will be easy by forcing the user to use a form for the deletion and
addition of parameters (where underlying code can then do the rest) but since
I will be accessing the database from another program (VB.NET application), I
would like to the design the db in such a way that I do not need a form to
make the neccesary changes (or would it be possible to use the db's form in
my application in such a way that it seems part of my application?)

ISTM that the best approach would be to implement the m:m relationship
with a joining table as usual, and then code a user interface on a
VB.Net form.

 

[John Nurick]

It's highly undesirable and never or virtually never to alter the design
of tables as part of ordinary database operations.

....or virtually never necessary...