I used the 'eval' because the sql statement in question is one of many that are got from a hash list populated by another program at another time, only some of which contain 'select ... into' statements. I could parse the sql statement and try to figure out what the table name is, then check for its existence, but it seemed to me the 'evel' was a more elegant way of doing it. Again, the perplexing thing, as I said to shmem, is that the code I showed you, which lives in its own module, is utterly unchanged whether I call it from a command-line module, or a tkx module. The command-line invocation works, the tkx invocation doesn't. I'm stumped. | [reply] |