> But if we cannot pass a user defined variable to theyoudatabase query builder then it makes the database-linked controls kind of weak. I hope thatcomplete that user interface soon.
It isn't straightforward to implement a clear interface for this : should it be global variables ? should it be a call to a function in the stack script ? should it be the content of a custom property ?
I'd suggest it would be more useful (possibly a little harder to do) to allow any valid Transcript expression in a query, perhaps surrounded by characters that don't normally show up in a SQL query (could "[" and "]" be used for this?). The database query manager would substitute the value for the expression before passing the query to the db library, whenever the query's used.
--
jeanne a. e. devoto ~ [EMAIL PROTECTED]
http://www.jaedworks.com
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
