Subject | Re: Bug in Firebird 2.1.1 (and Firebird 2.1.0) |
---|---|
Author | trtoms |
Post date | 2008-10-29T19:40:54Z |
--- In firebird-support@yahoogroups.com, "Leyne, Sean" <Sean@...> wrote:
have something like 50+ applications to migrate from the BDE and this
may take several months.
The particular application that caused this error can temporarily be
altered so that the alias names are not used for non-joined queries.
Is there no way that the new connection parameters can use sensible
defaults which enable compatibility with the BDE drivers?
Regards,
Trevor
><snip>
> Trevor,
>
>That makes sense. Looks like we'll have to roll back to FB2.0 as we
> I suspect that your application will not work with FB v2.1+, due to a
> limitation in the INTRBASE driver, which doesn't correctly handle new
> optional connection parameters. This problem also affects the early
> Firebird OBDC driver and the .Net 1.1 Providers.
>
> This is no way to work around the problem, aside from replacing the BDE
> from the application.
>
>
> Sean
>
have something like 50+ applications to migrate from the BDE and this
may take several months.
The particular application that caused this error can temporarily be
altered so that the alias names are not used for non-joined queries.
Is there no way that the new connection parameters can use sensible
defaults which enable compatibility with the BDE drivers?
Regards,
Trevor