Just an update....
Actually that wasn't the real case (but then again, how many other error messages are accurate to the problem).

because I had to specify the database.dbo.table, it was apparently expecting the full definition for each field in the select list rather than the implied table name being the alias. Sounds flaky huh??

I had to explicitly change the SQL to

mydatabase.dbo.mytable mytable, mydatabase.dbo.othertable othertable,
left outer join mydatabase.dbo.thirdtable thirdtable

in order for it to work... Hope you don't ever have to run into this... but if you do, a good heads-up...



>Whew!
>
>Glad I could point you in the right direction. :-)
>
>
>>Thanks for the input about the messaging from connection... I tracked the errors using aerror() 2nd item, and found the problem. Apparently, SQL is case sensitive on the pass through and didn't associate the column selection of
>>XDiagID.field with the FROM XDIAGID alias... (so stupid...)
>>
>>
>>>The modified ODBC driver saved as a separate Data Source Name.
>>>
>>>>>
>>>>>No more verbose message? Try going into the DSN and modifying it to show alert messages and see what you get then.
>>>>
>>>>Ok, I'm drawing a blank, what does DSN standfor.... or are you referring to the SQL Connection information