Golovko
July 7th, 2005, 01:46 PM
I have a table Location and a table Control for an Access mdb file.
I am programatically creating these tables using CDatabase.ExecuteSQL function. The Location table is created first and then then Control table, because Control has a fk into Location. Location however has an fk into Control. So after the two create statement, I execute an alter statement to add the new constraint to the Location table.
The problem is when I open the .mdb up in Access, it shows two tables when I open the Relationships window, Location and Location_1. Location_1 has the new constraint that I added with the alter statement. How can this be fixed?
I am programatically creating these tables using CDatabase.ExecuteSQL function. The Location table is created first and then then Control table, because Control has a fk into Location. Location however has an fk into Control. So after the two create statement, I execute an alter statement to add the new constraint to the Location table.
The problem is when I open the .mdb up in Access, it shows two tables when I open the Relationships window, Location and Location_1. Location_1 has the new constraint that I added with the alter statement. How can this be fixed?