Well, actually Ed's right so it's (of course, what was I thinking!)
not going to work in this situation, but for completeness' sake, in a
single environment, ie where the SQL is getting executed in the same
"place" that the UI is running, you'd have SQL something like
SELECT x,y,z FROM t WHERE [your where-clause stuff] AND z() ...
The function Z returns true so that it doesn't act as any kind of
filter, but it contains code that does the onscreen reporting.
See, horrible old style thinking. Except, of course, what's a UI for
if not interfacing the user to the processes... :-)
I'm being slightly sarcastic it's true (I am British after all), but
I still think in essence Ed's right about the UI/database layer
interaction
Regards
Mark Stanton
One small step for mankind...
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
