Hi,

>I must admit I was surprised not to get more support on this. It
>seems ambiguity is not to be tolerated. I'll have to recode some of
>our user tools :(
>
>It's sad though. I can see that results from ambiguous queries can
>on rare occasions be unpredictable, but most of the time they will
>run fine. Intolerance of all ambiguities makes the engine more
>accurate, but considerably more stupid.

More stupid? I don't get that... I've once spend hours of debugging
for a certain statements that worked fine on IB and totally failed on
MS SQL because of this!

As said before, abimguity = bad. I don't get it that you can accept
that the engine produces results A for one time, and might produce
results B for another run of the same report!



Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com

Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."