> Probably my english is so poor that I can not meke the point clear, I apologise. What I was referring to is that (from FB1 release note):
> ...
> Ambiguous JOIN statements are now rejected
> InterBase does not prevent you from submitting a statement like this:
> SELECT A.FIELDA, B.FIELDA
> FROM A JOIN B
> ON FIELDX = FIELDY
> WHERE FIELDA="99"
> ORDER BY FIELDA
> ...
> I think that THIS IS THE MAIN COMPATIBILY PROBLEM, not the Insert one. If you think that your old apps, with the Insert fix, will not encounter the above, ok, FB1 has to be fixed for old app compatibility. BUT I think that even with the Insert fix, you will not be able to run your old app against FB1 without change your code in the Joins (I had to do in my apps).

NO NO NO

I certainly don't have a problem with joins, I rarely use
them that way.

The problem is simply that EVERY automatic ( I'm listening
Tomas <g> ) INSERT is converted to an SQL format that is now
rejected.

JOIN does not come into this discussion!

> For current applications, the problem does not exist, since you have the source, you have only to recompile. If you manually build "bad" Insert SQL statement, you only have to make them "good" like you had to do with the joins. What's so terrible?

We are not complaining about new stuff - no argument. It's
all the existing - fully operational applications that can't
just have the server changed, and THEN be updated to take
advantage of the new features. I for one was hoping to check
out and deploy FB1 Final, THEN look at updates to those
programs that needed it, not to have to recompile and
re-test the whole lot first ( some 50 interrelated programs!
)

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services