I have delimited a little more the problem. If a remote application
crashes the server, it is probably that the problem is in the server.

In any case, I have tested the paths and aliases and still it fails.

When I said that I eliminated all UDFs, it was not completely exact.
I wanted to say that I eliminated my own UDFs.

In reality I use INVL function in a view:

DECLARE EXTERNAL FUNCTION INVL
INTEGER, INTEGER
RETURNS INTEGER
ENTRY_POINT 'idNvl' MODULE_NAME 'fbudf';


Then, I have a view that uses this function:

SELECT INVL(NUMBER_ITEMS, 0 ) FROM ....

But also my application fails if:

SELECT INVL(5, 0 ) FROM ....

The thing is these sentences are part of a report, the report always
woks fine. Then, when I return to other areas of my program, this
crashes the server, but not the above SQL sentence, although it can
be the initial cause.
If I substitute the INVL by a constant, everything works fine and my
app never crashes the server.

I am sure that fbudf.dll is fine, as I said, I installed Fireberd in
clean and new computers. Also, I have downloaded several times and
from several places the Firebird package from Internet to make sure
of its integrity.


At the end, I am not sure if the INVL is the guilty. Maybe it hides
the symptoms of the real problem. I think this because INVL has been
intensively tested by a lot of programers.

In any case, I need to use INVL function. I am sure that the database
is fine because I said, I have created the database several times
from zero.

Please, any idea?

Thanks




--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

> At 09:27 AM 19/01/2004 +0000, you wrote:
> >--- In firebird-support@yahoogroups.com, Helen Borrie

<helebor@t...>

> >wrote:
> > > At 10:46 PM 18/01/2004 +0000, you wrote:
> > >
> > > >I am using Firebird 1.5 RC8.
> > >
> > > What platform (hardware, OS) is the server running on?
> >
> >Hardware: Several: IBM Netvista, IBM ThinkPad, Dell, ...
> >OS: Windows XP Pro, Windows XP Home, Windows 2000 with

corresponding

> >service packs
> >Libraries: IBOjects in client side
>
> Are you using run-time linking of the IBO libraries?
>
> What have you done about the *Firebird* client libraries since

installing

> RC 8? Double-check the versions on those gds32.dll files *after* a

reboot,

> to make sure they are really what you think they are.
>
> Are you using a version of IBO 4.3 or higher?
>
> I am using IBO 4.3a with RC8 with no problems. I have the RC8

version of

> fbclient.dll, renamed to gds32.dll, and copied to all of the client
> locations where gds32.dll is expected to be for IBO (the system
> directory). (This is not the recommended thing to do in the field,

because

> it will break any InterBase clients on those workstations...but

it's what

> you need to do with old IBO apps if you don't want to customise

them for

> Firebird...)
>
> > > >This error appears in a sporadic way, and I cannot find the
> >pattern.
> > >
> > > So, which is correct? It always fails, or it sometimes works?

If

> >it
> > > sometimes works and sometimes fails, where do the failures

occur?

> >at
> > > login? when running a query? something else?
> >
> >It always fails after a certain time. The fail is using easy SQL
> >sentences like "SELECT * FROM TABLE1 WHERE ID=243543'.
> >Maybe a consult works fine 20 or 30 times, I list a report, I

return

> >and then it fails.
>
> I advise you to get a better report of the conditions where the

exception

> occurs and take it to the IBO support list.
>
> > > What connection path string(s) do you use in the applications?

I

> >mean
> > > *exactly* what connection path strings...
> >
> >I have tested several like:
> >
> >local
> >c:\program files\ramat\ramat.fdb
> >f:\ramat.fdb
> >f:\ramat.fdb and host=localhost
> >
> >remote:
> >f:\ramat.fdb and host=portatil
> >...
> >
> >I fact, I have tested a lot of paths, units and hosts
>
> Try using the database aliasing feature. It enables you to "soft-

code" the

> path into your application.
> In aliases.conf, enter something like:
>
> TheDB = f:\path\to\database
>
> Then your IB_Connection settings are simply
>
> Path: TheDb
> Server: either portatil or localhost
> Protocol: cpTCP_IP
>
> Or, if you are using the DatabaseName property directly, it will be
> localhost:TheDb
> or
> portatil:TheDb
> That, at least, will eliminate bad paths from the considerations.
>
> >Yes, some Firebird 1.5 installations have been done in new and

clean

> >PCs.
>
> /heLen