At 25/12/2001 02:24 PM, you wrote:

>I have just uncovered a problem with the IBX Backup Service component (and
>probably the others too). I am using Woody's code and IBX version 4.62. I
>have one computer running Interbase Open Source and the other running
>Firebird RC1. Interbase runs fine, but using Firebird I get the following
>message:
>
>Error: invalid transaction handle (expecting explicit transaction start)
>
>With the demise of the Mers list, there was a period when I was out of
>touch with the IBX newsgroup, but the problem does not appear to have been
>reported there. However, I don't think many of them use Firebird.
>
>Should I upgrade to RC2 and try again?

I would suggest that you do. I had a problem with the backup in FB, but
not the same. Now with RC2, I don't have the problem. The only problem
that I encountered when upgrading was ambiguous fields in queries. This is
a fix to a bug that apparently existed for quite a long time in IB.

Example of ambiguous field in a SELECT:

SELECT CLIENTNO, FIRSTNAME, BALANCE_DUE
FROM CLIENTS
INNER JOIN CLIENTORDER
ON CLIENTORDER.CLIENTNO=CLIENTS.CLIENTNO

Notice the field CLIENTNO in the fields returned and notice that it exists
in both tables. Before it wasn't an error because the engine simply took
one of them. I know that in this example CLIENTNO would be the same for
both. But, if BALANCE_DUE is found in both tables, it wouldn't contain the
same information and what guaranties that the information returned is the
right one.

Just keep in mind that you might have to look at your application carefully
before upgrading for these possible ambiguities.

Have a nice day.


Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)