>That's a good idea. We should implement an error log. This module is internal, but any time spent trying to figure out these problems, is time that we can't bill customers.

I'm trying to implement an error log. Right now I believe that our FoxPro backend is in a wierd state. Both the Release command and the Local command are erroring out.

When I comment out both commands, the code works fine but the error routing is not being called.

Below is the code used to call my error handler. I've placed this in all of the stored procedure because it seems this is the only way the LogError function will be visible.

On Error Do LogError With Program(), Message(), LineNo(), Message(1)

Below is the LogError function.

Function LogError
LParameters tcProgram, tcMessage, tnLineNo, tcCommand

On Error

Insert Into ErrorLog ( Program, Message, LineNo, Command, Occured ) ;	
				Values( tcProgram, tcMessage, tnLineNo, tcCommand, DateTime() )
				
On Error Do LogError With Program(), Message(), LineNo(), Message(1)

EndFunc