thanx Spike and Nat for the thoughts so far. as I said I inherited this stuff but it's a bit hard to say "hang on guys - you should be doing this..." when a clear alternative isn't apparent.
>> but I do think that you will end up paying a lot of maintenance tax further down the road. Spike, I hear ya, loud 'n' clear. this is my main fear (plus code readability) >> a trade-off between long term maintenance and short term development cost well, the two mods I did yesterday were real quick - after I spent the time working out how the bloody thing ticked. I got away with doing this with ASP because it was just a team of 2 and the best you could get was VBScript classes anyway (there was hardly any call for COM functionality) >> I also don't like the metaphor of a "WHERE CLAUSE" as part of my API >> because I like to think that the SQL itself is an implementation detail... me too. I'd bypass the whole issue and use sprocs but we can't (target db, org standards, etc) >> For instance, if there are really only 3 kinds of filters... that's the crux of it. It's mostly fueled by customer feature requests. We just don't know yet. I like the "queryFilter" CFC idea. worth looking into. seen any examples illustrating the point thanx again barry.b ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
