Commented by: @hvlad

It is nor recommended nor good way to create application in a such way and nobody promises it is even going to work.
I speak about load many different fbclient's at the same time into same process.
It look as exotic at least.

In your first sample it is easy to use fb3 client to make rmote connection to fb2.5 server and embedded connection to the v3 database.

In your second sample you should use single client at D:\Firebird\FB30

I see no reason to treat this ticket as too important therefore will lower its priority

Commented by: Nick (nick)

I have this problem when work with IBExpert.
I think It must be fixed or clearly stated in release notes.

Commented by: @asfernandes

> It is nor recommended nor good way to create application in a such way and nobody promises it is even going to work.
> I speak about load many different fbclient's at the same time into same process.
> It look as exotic at least.

I completely disagree. There should be no good reason for at least the client do not work in this way.

I do not talk about priority, but it's surely a bug and has nothing exotic.

Commented by: @hvlad

Adriano,

client works. The current issue all about embedded.

Commented by: @ibaseru

questions:

1. are AHandle returned by LoadLibrary different after 2nd LoadLibrary call?

2. what if after 2nd LoadLibrary you make a call in the first attachment, not in the second?

Commented by: Chau Chee Yang (cheeyang)

The issue should be fix. It is consider a bug. Loading both Firebird 2.5 and 3.0 fbclient.dll in the same process should always allow and encourage to do so as long as the application using match dll handle to access match firebird database. It doesn't violate any rules at all.

Loading both DLL in same process is useful for application that need to access both Firebird 2.5 and 3.0 database at the same time. One such usage is migrate the Firebird 2.5 data to Firebird 3.0 database.

Commented by: @hvlad

Chau Chee Yang,

read my answers above.

This issue can replay in Firebird 3.0 and Firebird 4.0 too.

Could you specify, please - what exact issue do you speak about ?
I ask because your previous comments was far from the original "issue".

Trying to attach to both Firebird 3.0 and Firebird 4.0 embedded database in a windows process with these steps:

1. Attach a firebird 3.0 database with embedded connection using firebird 3.0 fbclient.dll
2. Next, attach a firebird 4.0 database with embedded connection using firebird 4.0 fbclient.dll shall prompt

Error loading plugin Engine13
Module c:\firebird\4.0\plugins/Engine13 exists but can not be loaded

You should add Engine12 (from fb3) to fb4, configure it in firebird.conf and use fb4 fbclient to attach both fb3 & fb4 databases.

@AlexPeshkoff, both fb3 and fb4 plugins has DLL file using same file name but different file size. Moving engine12.dll to fb4/plugins may cause some dependency or compatibility issue that can be hard to trace later.

No issues, it's recommended way to open both types of databases in single process. Pay attention - I do not suggest to copy all plugins but for engine that does work.