---In [email protected], <alex@...> wrote :
 
 > I copied fbclient.dll to exe folder and get same result:
 > "Error loading plugin Engine12
 > Module c:\Program Files\Firebird\Firebird_3_0\plugins/Engine12 exists but 
 > can not be loaded
 > unknown win32 error 193"
 > 
 

   It means your app loaded fbclient.dll from "c:\Program 
Files\Firebird\Firebird_3_0\" not from app folder.
 

 

 > I'm using  Delphi and IBDAC components from Devart to access Firebird. 

 

   I have no idea how\where IBDAC looks for fbclient.dll
 

 > I'm sure this is not an embedded server connection. 

 

   Here you wrong. See below ...

 

 > The program is 32 bit as I mentioned and the Firebird server is 64 bit.
 

   If the app is 32 bit and tries to load dll with no path - it wiil not try 
64-bit system folder (c:\Program Files\)

 

 > I can specify location of fbclient as one of the connection properties.
 

   And you specify... what ?

 

 > All connections are local. 

 

   ...stop using "local" connection string and read the docs about embedded and 
connection strings.
 

 > The server is running on my development machine.
 > 

 > I wonder if there is other way to specify the database address for this 
 > connection to force some other plugin to get loaded?

 

   See above ;)
 

 Regards,
 Vlad
 

 PS 
https://www.firebirdsql.org/en/documentation/ 
https://www.firebirdsql.org/en/documentation/
 
https://firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-engine.html
 
https://firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-engine.html
https://firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-compat-winlocal.html
 
https://firebirdsql.org/file/documentation/release_notes/html/en/3_0/rnfb30-compat-winlocal.html
 https://firebirdsql.org/en/news/new-article-connection-strings-in-firebird-3/ 
https://www.google.com/url?client=internal-uds-cse&cx=010633460585558258518:jpoa5mcegvg&q=https://www.ibphoenix.com/files/ConnectionStrings_Fb3.pdf&sa=U&ved=2ahUKEwiKi5OPh6fiAhVS-yoKHezDAfQQFjACegQIDxAB&usg=AOvVaw1DquWWXNyoKEyozPcOQ6UZ
 


Reply via email to