Viewing 15 posts - 55,666 through 55,680 (of 59,098 total)
Got part way there using a limited triangular join... it spawned 2 times as many rows as the original count of both tables and that's with just a couple of dates... I...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 8:39 pm
Eugene... wanna post some data from the file, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:43 pm
Guess you can't actually look into a book on Amazon anymore, huh ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:34 pm
Ummm.... not quite that simple... need to distribute a batch of QTY 15 issues against 4 batches of QTY 5 each and do the calculation and forward the remainder. Lot's...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:29 pm
That's why the stored proc method is better.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:25 pm
Thanks for the feedback, Kung Lao.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:23 pm
Is GROUP BY what you're looking for?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 7:33 am
This sounds like the text version of a "name/value" table... I'm with MrPoleCat... if you could post a bit of the text table, perhaps we could help. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 7:32 am
I don't know what sqlcomm1.ExecuteNonQuery() does because I'm no GUI programmer... UPDATE's are actually a form of a query and that may be your problem (but dunno for sure). But...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:54 am
Heh... and I just "assumed"... we all know what happens when you do that, eh ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:34 am
Well... that depends... do you want to shrink the file or not? The NOTRUNCATE causes the "freed file space to be retained in the files". If you want to actually...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:29 am
Heh... not unless some fool thought it would be a good place to store permanent data ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:19 am
Sum of the quantities for a given part. Quantity is add if the RowType is 'Receive', Quantity is subtracted if the RowType is 'Issue'. Another name for 'RunningBalance' might be...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2007 at 6:15 am
Haven't figured out the long term/shorterm things yet, but here's some more realistic data to play with... created a single "work" table just to help imagine what's being received and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2007 at 11:18 pm
Heh... I think you're making a mistake using FLOAT on the RATEs (which I assume will be currency amounts of some sort). If you don't think so, try this...
--Jeff Moden
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Change is inevitable... Change for the better is not.
July 24, 2007 at 10:48 pm
Viewing 15 posts - 55,666 through 55,680 (of 59,098 total)