Hi Greg:

At first thank you for your reply.

There is an "on error" procedure but only shows a message and it has been the procedure I've been using during years. Now I changeg and I programmed error events on forms but none has a CLEAR MEMORY or similar.

I'm coming from Clipper and I wanted to use all the files UDF functions which gave me some bread for almost 20 years and still do.

Those are the functions and procedures that suddenly started to cause problems. One opens a file, other open the indexes, other brings a field or the description field.

For example: I have a form that input a new or modify an existing client. Every client has different "Provincias" (Estates) has different pay conditions. I don't open explicitely these files but when I chose a client from a help form every field of the client's file searchs for its descriptions to another file I open, read and close. Only the client's file is open all the time till I close the form.

Well. My problem ocurrs when I do this executing a form from another form (click on a grid that contains the name of many clients and I want to know all the data of a particular client.

Think I execute this near hundred of times in a form. If I debug it I'll probably see my finger decrease an inch in an afternoon...

I gues you know: When I debug it all works wonderfull.. Slow but wonderful

Thank you

Héctor