in reply to eval doesn't work under tkx

can't remember exactly but I'm fairly certain that DBI provides such basic additional functionality as checking for table existence. so you shouldn't have to eval in the first place. if you cannot find this in DBI docs or others help, there's also the implementation specific (M$) system table in Access, which contains information about all the tables etc and can be queried.
the hardest line to type correctly is: stty erase ^H

Replies are listed 'Best First'.
Re^2: eval doesn't work under tkx
by nyj (Novice) on Jul 16, 2010 at 06:01 UTC
    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.