Viewing 15 posts - 57,736 through 57,750 (of 59,067 total)
I think you may want to look into the reason for the backoffice DB starting up twice... that should not happen...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 8:12 pm
I concur with Remi... a simple polling job is not going to be any load on the server at all. We have a couple that run using the undocumented but...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 8:07 pm
If the tables already exist, there should be foreign keys in the child tables (the "many") that point to the parent tables (the "one").
If not, then, as Sreejith suggested, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 8:01 pm
You can fool around with user names, if you want, but those can always be tricked especially when users make the mistake of sharing logins...
If your Windows network is setup...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 7:56 pm
This should do the trick... the SELECT is where the rubber meets the road... the rest of the stuff is just setting up for the demo of the SELECT...
--===== If...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 7:22 pm
Actually, I've resurrected some old code I was working on to make a WebTask that would make some pretty output... the output does not yet list the primary or other...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 6:20 pm
| I also realize that there is no 'Descritpion' value for a column in the DB and that the... |
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 5:02 pm
Not a problem... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 4:48 pm
Nope... new columns always get added to the "end" of the table if you use just an ALTER.
However, if you go into Enterprise Manager to design the table (add the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 4:20 pm
By the way (drum roll, please), congrats on the more than 7000 posts you've made ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 3:55 pm
True enough... you won't be making a view out of it, for sure ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 3:54 pm
Bingo!!
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 3:44 pm
Yep... and you've nailed the key to it... exclusive access... now, what table(s) will a developer ALWAYS have exclusive access to?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 3:32 pm
Yap... we've all written "those"... see the update I just posted to my previous message...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 3:23 pm
Sure, Remi... thanks for the interest...
Personally, I think triangular joins should never be used because it's an absolutely insane form of RBAR (a "Modenism" for "Row By Agonizing Row"). Here's an example...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2006 at 3:09 pm
Viewing 15 posts - 57,736 through 57,750 (of 59,067 total)