Good suggestion, but that's not it. My error routine basically does nothing more than trap the error code and display the message (I'm still in the process of developing it and this was the intial step ... just trapping the error). Anyway, this error does not appear after another error has happened (which would be the situation in what you suggested), so it's not the error handler that has the problem ... VFP is not calling the error handler for some weird reason. Why?

Bonnie


>ok then...maybe your error routine has the error, in that case you get the error message directly from fox, it doesn't do a recursive call, and it's not suupposed to, maybe your error handler assumes there's a table where there's not. That would at least explain the error message coming from fox and not your routine