pwalter83 (7/24/2013)
ChrisM@Work (7/24/2013)
pwalter83 (7/24/2013)
ChrisM@Work (7/24/2013)
pwalter83 (7/24/2013)
ChrisM@Work (7/24/2013)
pwalter83 (7/24/2013)
ChrisM@Work (7/24/2013)
Lowell has already asked but the question remains unanswered: why do you want to hold the same data in two places at once?Hi,
The reason is - The same data needs to exist in two related tables is bacause this is part of the web project consisting of many sub-pages. If the value in one sub-page is changed then that saved value in the main webpage should be updated accordingly.
Each of these webpages are linked to individual tables so in fact the changes are to be made at the SQL level first.
Surely the main page and the subpage should be reading the same value from the same table?
Wish it was ? But no, as I mentioned before, each webpage is associated with a different table.
The main webpage is populated using the tables which are linked to the sub-pages and so the same columns exist in different tables. This implies that the tables should be normalised so that if any value is updated using the sub-pages, the change should be reflected in the main webpage.
This looks correct: "The main webpage is populated using the tables which are linked to the sub-pages". That's fine - a subpage and the main page can read the same data from the same table.
The rest of it is bonkers. It's the wrong way round.
I am not sure where we are going with this debate. The webpages have already been setup and they are working properly. The only thing left to do is to normalise data so that the change on one table is reflected on the other table and hence updated accordingly on the main webpage.
Do you have any ideas or suggestions to accomplish this ?
Sorry, no I don't. I can only reiterate this:
"The only thing left to do is to properly code the pages so that the change on one page is updated accordingly in the table and hence reflected on the other page."
- and wish you luck, because this is probably the thin end of a very big problem wedge.
Sorry Chris, I know you have helped me before but this time I know that the solution lies in normalising the database and not changing the webpage coding.
Heh that's okay Paul. I'd be interested to see how you get on with this - not in a "I told you so" kinda way, but curiosity. I can't see how it can cause anything but problems, and your confidence in the resolution tells me I've got the wrong end of the stick 😉
For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden