not harsh.. over the years, I've seen plenty of stuff that was boilerplate 
from one of the programming books.. and then snip snip snip all over the 
place, without removed the original copied clues

one of my mantras has always been, just cuz you CAN do it in one query, 
doesn't mean you SHOULD do it in one query.. in the early days, I'd do 
multiple queries.. later, and now, scan loops

honestly, this kind of convoluted query isn't pushing the envelope.. it's 
always written long before there's enough data to truly understand if it has 
failure points, missing or duplicated data, etc.. fun to decipher, tho :-)

--

Steven Green
Myrtle Beach, South Carolina, USA

http://www.OasisTradingPost.com

Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Bernie van't Hof"  wrote in message 
news:6037df67$1@pnews.thedbcommunity.com...

Gee isn't that a bit harsh?
My 2c: Not using this sort of stuff would have been like driving a
Porsche at 30 mph.

On 26/2/21 2:13 am, Steven Green wrote:
> I hate crap like that.. it's been working for 30 years by accident, or it 
> doesn't work and they don't know that.. either way, I'd never do it that 
> way.. I'd never even think to do it that way.. it's probably based on some 
> theoretical thing that Dan or Mike put in one of their books :-)
>
> -- 
>
> Steven Green
> Myrtle Beach, South Carolina, USA
>
> http://www.OasisTradingPost.com
>
> Collectibles and Memorabilia
> Vintage Lego Sets and Parts
> - and Paradox support, too
> "Bernie van't Hof"  wrote in message 
> news:6036fe20$1@pnews.thedbcommunity.com...
>
> This one's been working for 30+ years but I can't write a unit test
> until I know exactly what it is meant to be doing:
>
> Query
>
> Debtor |   A/C#   |  MyRef   |    Dr    |      Cr      |
>         | check _a | check _m | check _r | blank        |
>         | _a       | _m       | blank    | _r, calc sum |
>
> Endquery
>
>
> Any ideas?
>