R>> What do you plan to do with ARM-based jaybird*.dll? WinCE
R>> is not (yet?) supported by FB, so you should not be able
R>> to compile fbclient.dll or fbembed.dll for it (I assume that
R>> in your case VS 2005 + ARM = WinCE).
R>> Without fbclient.dll or fbembed.dll you won't need jaybird*.dll
R>> too - it is just a wrapper translating Java calls to FB API
R>> calls and vice versa.

> Good news!

Hmmm... did I wrote something wrong? I thought that my previous paragraph
means exactly the following: "Since WinCE is not supported, you won't have
fbclient.dll for WinCE. That means - no connection from WinCE to Firebird
_unless_ you use our wire protocol implementation over TCP (and assuming you
can connect via TCP)".

> We need to develop a thin winCE client to connect to our firebird db, so
> we are searching the most routable way to do such a thing. We are at the
> first step and, since we are Delphi-oriented programmers, we need to look
> at Java or C# way to build the first "Hello firebird from WinCE"
> application.

For Java - the "main" class is
org.firebirdsql.gds.impl.wire.AbstractJavaGDSImpl. For C# - check the
sources of .Net provider, there's few classes each supporting part of the
protocol. Both drivers provide implementation of the Firebird's wire
protocol over TCP, so you have to choose the language now :-)

> It also seems to me that I have forgotten something but, having
> heard your news, I don't need to re-build jaybird.. But if you
> are looking for a "dummy-builder", I can retry at your convenience.

Thanks!

Roman