Which is precisely why I ALWAYS do a project with both ends of the sprectrum being in
on the decision process (Management & IT). What good is a system that you bring in
house only to have it a technical OR Business Solution misfit?
BTW...although sometime the shoe fits...but why is management
Ahem -- 30 Days Dave? Admittedly it's a nice product and very easy to use but 30 days
is stretching it just a wee bit. Not impossible but it would have to be a
Chief/Cook/Bottlewasher operation, (you know how those confused powers that be that
keep changing their minds (13 times on one screen
First off those nested Loops are downright scary (reminds me of code I found as a QA
manager when the programmer was stoned at the time) --
Ever try
1) performing the selects at TCL individually to make sure permissions haven't gotten
wacked
2) Pulling out that code alone and running it with
Well -- the key is indexed...and so is the date field so the caveat does not apply in
this case -- more likely the elusive version 8 is the answer
--
Debster
--
>From Lee Bacall:
A bit of a caveat in making selects against indexed keys may be helpful...
If one is d
On D3 VERION 7.3 what is the syntax to use compares other than = if you are using an
indexed dictionary in the statement. It seems to return the correct items if it is
simply looking for an equal condition but anything other, such as > < etc. It appears
that it does not use the index, but ra
