| Subject | Using ADO.NET and fbembed.dll with FreeUDFLib.dll |
|---|---|
| Author | Alexander Gräf |
| Post date | 2004-12-10T11:00:06Z |
Hello,
just some information:
When using ADO.NET with fbembed.dll, the documentation states, that there is no need to, and you must not rename "fbembed.dll" to "gds32.dll". However, if you are using "FreeUDFLib.dll" for example, operations fail because gds32.dll needs to be available. So you need to copy and have both a "gds32.dll" and a "fbembed.dll" in the same directory/path.
I'm posting this on the general support, because I'm sure this also happens with other components which depend on fbembed.dll. Combining this with an UDF which does call functions in gds32.dll, the above described problem appears. The error message is for example:
invalid request BLR at offset 499
function BLOBASPCHAR is not defined
The only way for me to find out what was happening was the usage of Sysinternals NTFileMonitor, to trace file access and get a clue about the missing gds32.dll.
Regards, Alex
just some information:
When using ADO.NET with fbembed.dll, the documentation states, that there is no need to, and you must not rename "fbembed.dll" to "gds32.dll". However, if you are using "FreeUDFLib.dll" for example, operations fail because gds32.dll needs to be available. So you need to copy and have both a "gds32.dll" and a "fbembed.dll" in the same directory/path.
I'm posting this on the general support, because I'm sure this also happens with other components which depend on fbembed.dll. Combining this with an UDF which does call functions in gds32.dll, the above described problem appears. The error message is for example:
invalid request BLR at offset 499
function BLOBASPCHAR is not defined
The only way for me to find out what was happening was the usage of Sysinternals NTFileMonitor, to trace file access and get a clue about the missing gds32.dll.
Regards, Alex