> >>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;
>

I wonder if it's just a corrupt copy of the dll? on the PC in question
Alan

>
>
> /* 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.
>
>
>
> We have tried using all 3 of the Functions mentioned declared with and
> without FREE_IT, so my guess is that this is having no effect, and maybe
> I would need a copy of the freeUDFLib.dll which has been compiled with
> the $Define FREE_IT uncommented, I cannot seem to get that to work in my
> Delphi environment.
>
>
>
> Regards
> Martin
>