i got type 2 with embedded-server working now.
i need to put javaw.exe in the root directory of the embedded-server,
this is working for testing purposes, but not for installations at our
custumers.
Besides i'm really impressed by the perfomance of the type 2 driver ,
it's nearly 100% faster for selects than type 4, even faster than
interclient.

mfg
Carsten


Ryan Baldwin wrote:

> Hi Carsten
>
>
>>>>>>>>>>>>>>>>>>> FROM PRVIOUS
> POST>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>> I've made an UDF function. When i put the \UDF directory in the root
>> path of my application, it doesn't works. I'm forced to put the UDF
>> directory in the \bin of my java installation (C:\Program
>> Files\Java\j2re1.4.2_01\bin). Same thing with firebird.msg.
>
> I need too look into some issues regarding this - I'm not entirly
> sure which sequence of directories
> fbembed.dll runs through and appends '/UDF' too when loading a UDF
> dll...
>
> You should find though that if the 'launcher' exe is in what you
> consider too be the your root directory
> then it should work - so for example if you copy java.exe or
> javaw.exe into your app's root directory(the same
> directory that contains the UDF directory) - and ensure you execute
> the exe from that location - it should work.
>
> One might imagine that setting the working directory
> should work - but I havent seen this work - the problem presumably
> down too where fbembed.dll checks obtains a
> list of directories too search.
>
> I'm not sure if simply requiring that the 'laucher' for the java
> application be in the root of the fb embedded
> directory structure is an acceptable solution - its certainly the
> simplest from my perspective and I dont see
> a problem with this - But what do you think ?
>
> ps. You should also find a similar problem when fbembed.dll needs to
> load the intl dll(s). And this has a similar
> solution.
>>>>>>>>>>>>>>>>>>> END: FROM PRVIOUS
>>>>>>>>>>>>>>>>>>> POST>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>