I'm just curious about is there any incident report about this:

SELECT
Matricula,
M.Nombre AS Nombre_Marca,
Modelo,
T.Nombre AS Nombre_Tipo,
NumTarjeta,
Clase,
Ambito,
ExpedicionTarjeta,
CaducidadTarjeta,
NOMBRECOMPLETO(C.RAZONSOCIAL,C.APELLIDO2,C.NOMBRE) AS Nombre_Completo, --*
DOMICILIOCOMPLETO(SV.Sigla,C.ViaPublica,C.NumeroVia,C.Escalera,C.Piso,C.Puerta) AS Domicilio_Completo, --*
MUNICIPIOCOMPLETO(C.CPostal,C.Municipio,PR.Nombre) AS Municipio_Completo --*
FROM
MAVEHICU
INNER JOIN MAMARVEH M ON (M.CODIGO = MARCA)
INNER JOIN MATIPVEH T ON (T.CODIGO = TIPOVEHICULO)
INNER JOIN MACLIENT C ON (C.NIF = PROPIETARIO)
INNER JOIN MASIGLAV SV ON (C.SiglaViaCod = SV.Codigo)
INNER JOIN MAPROVIN PR ON (C.Provincia = PR.Sigla)
WHERE
CADUCIDADTARJETA BETWEEN :DFecha AND :HFecha
ORDER BY
MATRICULA;

--* stands for stored procedures in an external dll

runs fine most of times, but suddenly server raises an access violation (running stand alone) or simply hangs (running as a service) when
preparing it.

I found problem is in external module .dll Stored code is very simply (just string concatenation) And it fails randomly.

Any idea?

I found it.

My stored procedures were compiled with just one package: edb202r2007run.bpl
This implies other vcl packages implicity included. In a *more than one session on server* use of string stored functions causes random a.v. at
server side.

Now, I compiled all .dll with no packages and a.v. are gone. (but my deployment package is some MB larger )

Tiago,

<< I found it.

My stored procedures were compiled with just one package:
edb202r2007run.bpl This implies other vcl packages implicity included. In a
*more than one session on server* use of string stored functions causes
random a.v. at
server side. >>

Wow, that's a tough one to find, so I'm glad you found it out instead of me.


Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com