sanity check - Relaltionship & table change

[NetworkTrade]

I need to add a new field to a table.

I receive the warning prompt that I can't change the table design because
the table's pre-existing relationships.

The table change/add is very minor...but I see they have a alot of queries
involving this table.

Must one document all these relationships, delete them temporarily, make my
table change - and then reconstruct all these relationships?

Actually as I type this I am inclined to think maybe perhaps copy table,
change - and then rename....

advice welcomed...thanx....

 

[Rick Brandt]

I need to add a new field to a table.

I receive the warning prompt that I can't change the table design
because the table's pre-existing relationships.

The table change/add is very minor...but I see they have a alot of
queries involving this table.

Must one document all these relationships, delete them temporarily,
make my table change - and then reconstruct all these relationships?

Actually as I type this I am inclined to think maybe perhaps copy
table, change - and then rename....

advice welcomed...thanx....

Adding a new field should not affect existing realtionships so you shouldn't
have to do anything. That warning should only be displayed if you are trying to
delete or change a field that is already participating in a relationship.

 

[NetworkTrade]

hmmm ....well the warning prompt comes up when I first attempt to open the
Table in Design View - that I can not change the table and "do I want to open
it anyway?"...

so have just taken that warning at face value and did not try to add a
field....

interesting - - will experiment and see....

 

[NetworkTrade]

Access2002 and it is a split db.

This definitely is not the first time I've seen this error message. I
consider it standard. When you attempt to open a Table in design view it
prompts/warn that "the Table properties can not be changed because of ....."
and "do you want to open the table in design view anyway?" one enters "yes"
and it opens in design view.

In most cases it has been easy enough to temporarily delete relationships
and change a table. In this case there is many relationships due to
queries.....

Obviously still I am a little fuzzy on the rules on this - - will experiment
some....

 

[Rick Brandt]

Access2002 and it is a split db.

This definitely is not the first time I've seen this error message. I
consider it standard. When you attempt to open a Table in design view it
prompts/warn that "the Table properties can not be changed because of ....."
and "do you want to open the table in design view anyway?" one enters "yes"
and it opens in design view.

In most cases it has been easy enough to temporarily delete relationships
and change a table. In this case there is many relationships due to
queries.....

Obviously still I am a little fuzzy on the rules on this - - will experiment
some....

If it's a split app are you in the back end file when you do this? That is the
only place you can make design changes to tables.