d-coding the
SELECT statement, and get the same errors.
This sounds like a total Catch-22 to me, which must mean I'm doing
something wrong. Help!
Thanks in advance!
Brian Troxell
[EMAIL PROTECTED]
Brian Troxell wrote:
> I'm getting an error when forming SELECT statements using the new 7.1
> EXECUTE command. The error states, simply, that there was an unexpected
> SELECT within the EXECUTE command.
>
> Which leads me to ask: can I actually form SELECT statements us
to be doing?
Thanks in advance.
-Brian Troxell
[EMAIL PROTECTED]
