>What code is being run at the point of the error? Do you have any error logging in place that will store information about the error when it occurs? At a minimum, you should be storing the procedure/method name and line number.
>
>>In VFP 8 -
>>
>>A user reports that they get Error 11 and Error 17 sometimes, but not always when running a form containing a names and addresses in a listbox-looking format. The error occurs when they right-click the mouse to choose a menu item from a menu that has choices such as Add an entry, Delete an entry , Update an entry, etc.
>>
>>I found Error 11 can be caused by 4 different reasons on the Microsoft knowledgebase. I didn't find Error 17 in the Microsoft knowledgebase.
>>
>>Any ideas? Thanks ahead of time.
>>Hopefully I won't be a stranger here any more. I've got some VFP work waiting in the wings.
>>
>>Steve Kramer
>>Software Developer


Lacking further knowledge, I am assuming these are Foxpro error numbers:

Function argument value, type, or count is invalid (Error 11) -- A value passed to a function is not of the expected data type, or the value of the argument is out of range for this function, or you are passing too many arguments to a function.


Table number is invalid (Error 17) -- work area on SELECT n, where n is outside range of 0 - 255


Barbara is correct, more information is needed to solve your problems. On all versions of FOX, you can trap errors with ON ERROR...

For example:

ON ERROR DO HANDLERROR with ERROR(), MESSAGE(), MESSAGE(1), LINENO(), SYS(16)
.
.
.
FUNCTION HANDLERROR( lnError, lcMessage, lcMessage1, lnLineNo, lcProgram
.
.
.
* Handle recording / recovery from errors

NOTE -- ERROR methods in objects and TRY...CATCH ( beginning in VFP 8 ) intercept errors before the global ON ERROR.