Subject Re: Unsupported Column Type: 0
Author sllimr7139
Hi Hellen,

I goofed. I just made your suggested changes and compiled it with my
old version of Marathon (v1.6) and it compiled. I was then talking to
my wife about what you had suggested and I started thinking that your
changes shouldn't have made any difference. So I went through and
tried my original code in Marathon (v1.6) and everything compiled.

So my problem lies with Marathon (v3.0.0.50) and not necessarily with
my code.

Although I can see where your coming from I still think that, from a
logic pov, my original code should work without confusing the database
engine. So I'll ask again, because I'm now wondering what kind of
consequences my original code could have vs. your explicit code, why
would the explicit table naming make any difference for the select on
the IN clause. Wouldn't the brackets provide enough logical
seperation for the engine to properly determine what columns are
coming from which tables?

BTW, I did go with your code. I now have to go back and take a look
at the Trigger editor and see what has happened to it.

Thanks again,
Ryan.