> From: "James Conley" <Conleyj at kubota-kma.com> > ... > The final product is a single [demoralized?] table ... Would that be the TBL_EEYORE table? I get this image in my head of a database object moping around complaining about how much bad data it contains, no ever cleans it up, no one every queries it, what's the point, etc. Sorry, couldn't resist. Here's the tip. <tip type="Isolating code bugs" author="John Brooking"> If you can reproduce a bug but still cannot quite figure it why it's happening, take the code you suspect is the problem and try it elsewhere with less unrelated code around it. Try to narrow it down to just the bare minimum you need to set up a simple test case. If it still doesn't work, you've now confirmed which code is the problem, and can set about researching it with more confidence, and asking others about it with less background noise. If it does work, add code back into to the test script from your original script little by little, and see when it breaks. Alternately, take your original code and stript it down little by little until it works. Sometimes one's easier than the other. Either way can help to isolate the problem. </tip> - John -- This message may contain information which is private, privileged or confidential and is intended solely for the use of the individual or entity named in the message. If you are not the intended recipient of this message, please notify the sender thereof and destroy / delete the message. Neither the sender nor Sappi Limited (including its subsidiaries and associated companies) shall incur any liability resulting directly or indirectly from accessing any of the attached files which may contain a virus or the like.