-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Dew wrote:

>>>and you're sure its the F_MID UDF? I've used it for years and never
>
> struck
>
>>>memory leaks from it.
>>>Alan
>
>
>
>
> Almost 100% sure, if we comment the following lines out of a stored
> proc, and then run it the memory does not increase, if we leave them in
> it increases;
>
>
>
> /* Convert the incoming status to one of our own for display
> purposes.*/
>
> alocation = F_LEFT(:V3_LOCATION,1);
>
>
>
> blocation = F_MID(:v3_location,2,5);
>
> blocation = F_RTRIM(:blocation);
>
>
>
> /* blocation holds the location without the c_ or b_ identifier before
> it, so this is the value you would */
>
> /* post into either the desp_car or desp_base field according to
> whether alocation is a b or a c */
>
>
>
> We have this stored proc at other sites, the only difference we can find
> with the other sites with no problem is the line containing the f_MID.
>

And what if :v3_location is less then 2 chars ?

blocation = F_MID(:v3_location,2,5);

How F_MID behaves in such case ?
Or v3_location is NULL for example ?

Regards
Boguslaw Brandys
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCzT8gtuGICzHOh+YRAmbGAJ9eBJRr8Am1lHeCxcThMMrbSEDfjQCcCsJ2
1bfFM5Mv9NP2dKq9Z23dHJs=
=/Rr6
-----END PGP SIGNATURE-----