March 28, 2012 at 12:26 am
I am having difficulty enabling 'cascade update' between a reference table, (say - Job Status), and multiple columns in a data table (say - Jobs).
(My real problem involves Geological Mineralization Logging codes, but they are a bit obscure...)
In 'Jobs', suppose there are three columns as follows - Job Status, Paperwork Status, and Preparation Status.
I can easily link the Status Code reference table with each of the three columns, to ensure they use the same set of 'lookup'codes. No problem.
But suppose someone wants to change the Status Code in the reference table? (Which some Geologists will invariably want...). You would logically set Cascade Update to handle this.
However as soon as you do this on more than one column, you encounter a 'possible circular reference' problem, and SQL Server rejects thechange.
Any suggestions for what I would have imagined would be a common enough requirement?
March 29, 2012 at 11:51 pm
A little more details of your tables would help.
Does the job status table have just the one column for the status like the following?
Job Status
------------
Done
Incomplete
Not started
Then is the problem when trying to change, for example, 'Done' to 'Finished'?
If so, what you should do is add an Id column and link that instead.
If I have misunderstood your question, please give a little more detail so someone can help you more.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply