The Wish List contains a few entries requesting improvements to VFP error messages. However, none lists (many) specific messages, although some added comments do so.

The idea behind this proposed submission is to attempt to rectify that situation by stating sufficient different requirements as to strongly suggest the kind of improvements desired for ALL of VFP's error message.
I have done this using the messages numbered between "***" to 099.

I am requesting your comments, additions or deletions to what follows.
In addition, I need to know if you believe that this conveys the general requirements sufficiently so as to serve as a "template" for the VFP Team to complete the balance of the error message in VFP without having to detail each remaining one.

-------- START potential Wish List content ---------------------------------------------------------------------
While VFP's error message content is often adequate in the interactive development environment, the majority are significantly lacking in helpful detail when emitted in the runtime environment, especially at customer sites.
This wish attempts to give the VFP Team a "template" showing the kind of change/augmentation required to make the error messages far more utilitarian regardless of the running environment.
The general principle is that the specific factors involved in the error are also provided in the error message..

CRITICAL: In every case the "call stack" content is to be displayed or at the very least the name of the program component in which the error is manifest.

*** *bad date*
- The specific whole command (operation) causing the error should be given, with the values of all arguments involved.

*** Cannot allocate screen map
*** Cannot create program workspace.
*** Cannot find spell check program.
*** Cannot find the beautify program.
*** Cannot find the spell check program.
*** Cannot find the wizard program.
*** Cannot open configuration file.

*** Fatal error nExpr reporting error nExpr.
- The Help says: "Record your recent actions while using Visual FoxPro and then call Microsoft Support.".
-- *IF* a "Dr. Watson Error Report" is available for sending here, it should say so.

*** *Interrupted*
*** Invalid compact EXE file. Rebuild EXE.

*** Invalid or duplicate field name.
- The specific field name should be given and the table name would also be helpful.

*** Invalid or missing EXE file.
- The specific EXE file name should be given.

*** Logical expression required
*** Popup too big, first nExpr entries shown.
*** Product has not been properly installed.

*** Source code not found.
- The specific file name should be given.

*** Source code out of date.
- The specific file name should be given.

*** The Remote View Wizard was unable to obtain column information for this remote table. This may be the result of an ODBC error, or the remote table may not be owned by the current user.
*** Unable to locate desired version of Visual FoxPro.

*** Unable to process error.
- The Help says: "Record your recent actions while using Visual FoxPro and then call Microsoft Support.".
-- *IF* a "Dr. Watson Error Report" is available for sending here, it should say so.

*** Unknown error code nExpr.
- The description says: "Record your recent actions while using Visual FoxPro and then call Microsoft Support.".
-- *IF* a "Dr. Watson Error Report" is available for sending here, it should say so.

*** Visual FoxPro cannot start.

1 File "name" does not exist.

3 File is in use.
- The specific file name should be given.

4 End of file encountered.
- The specific file name should be given.

5 Record is out of range.
- The specific file name should be given and the record number sought should be given.
- The Help detail also says that the cause is that "The current index does not match the table". This is not the sole possible cause.

6 Too many files open.
- It would help if the name of the file where the error was encountered was given.
- The Help detail says "Visual FoxPro has attempted to open more than its internal limit of files.".
-- IF there are other factors/locations that could cause this error (config.sys, etc.), it would be helpful if they were mentioned.

7 File already exists.
- The specific file name should be given.

9 Data type mismatch.
- The specific whole command (operation) causing the error and the content of the fields/variables involved, should be given.

10 Syntax error.
- The specific whole command (operation) causing the error should be given.

11 Function argument value, type, or count is invalid.
- The actual function name, the argument number, the expected/passed types or values, or the count received/requird should all be given.

12 Variable "variable" is not found.
- The specific whole command (operation) causing the error should be given.
- The Help says that a variable or a field name can cause this.
-- The message should state EITHER 'variable' or 'field name' as appropriate.

13 Alias is not found.
- The specific whole command (operation) causing the error, and the alias (name) should be given.

15 Not a table.
- The specific whole command (operation) causing the error, and the specific table name should be given.
- The message should also be changed to say: "Not a table - incorrect header".

16 Unrecognized command verb.
- The specific text causing the error should be given.

17 Table number is invalid.
- Is this really a 'table number' or is it a work area number? (I doubt it is a 'table number')

18 Line is too long.

19 Index file does not match table.
- The Help for this states: "The index expression for the current index uses variables that are not contained within the current table.".
-- a) I think this can apply only to .IDX files. If that is true, shouldn't that be stated?
-- b) Since 'variables' are not contained in tables, shouldn't the correct word be "fields"?

20 Record is not in index.
- The Help for this has two lines and states:
"A key field of the table in use has been modified without the index having been active.
Apply the REINDEX command to the table file."
-- a) I think this can apply only to .IDX files. If that is true, shouldn't that be stated?
-- b) The second line should add "with the applicable .IDX file open to cause it to be REINDEXed.".

21 Length of variable strings exceeds amount of memory.

22 Too many variables.
- The Help for this states: "The maximum number of variables that can be created has been exceeded.".
-- It would be most helpful if the description also mentioned that MVCOUNT could be set in config.fpw to address this.

23 Index expression exceeds maximum length.
- The Help for this states: "The index expression for this index exceeds the maximum length of 220 bytes.".
-- Giving the index name would be helpful.

24 Alias name is already in use.
- The specific whole command (operation) causing the error and the specific alias (name) should be given.

26 Table has no index order set.
- The specific whole command (operation) causing the error and the specific table name and alias should be given.

27 Not a numeric expression.
- The specific whole command (operation) causing the error and the specific table name and field name should be given.

30 Row or column position is off the screen.

31 Invalid subscript reference.
- The specific whole command (operation) causing the error and the specific array name, the value of the (invalid) subscript supplied and the maximum value allowable should be given.

34 Operation is invalid for a Memo, General, or Picture field.
- The specific whole command (operation) causing the error and the table name and the alias name should be given.

36 Command contains unrecognized phrase/keyword.
- The specific whole command (operation) causing the error should be given.

37 You must use a logical expression with FILTER.
- The specific whole command (operation) causing the error and the table name and the alias name should be given.

38 Beginning of file encountered.
- The specific whole command (operation) causing the error and the specific table name and alias name should be given.

39 Numeric overflow. Data was lost.
- The specific whole command (operation) causing the error should be given, with the values of all fields/memvars involved.

41 Memo file "name" is missing or is invalid.
- The specific whole command (operation) causing the error and the specific table name and alias name of the associated 'base' table should be given.

42 The LOCATE command must be issued before the CONTINUE command.

43 There is not enough memory to complete this operation.
- The specific whole command (operation) causing the error should be given.
- The Help states: "Free some memory currently in use and try this operation again.".
-- It would be helpful if the Help listed some ways to accomplish this.

44 Cyclic relation.
- The specific table name and alias name should be given.

45 Not a character expression.
- The specific whole command (operation) causing the error should be given, with the value of the field/memvar involved.

46 Expression evaluated to an illegal value.
- The specific whole command (operation) causing the error should be given, with the value of the field/memvar involved.

47 No fields found to process.
- The specific whole command (operation) causing the error should be given, with the name of the table and the alias involved.

50 Report file "name" is invalid.

52 No table is open in the current work area.
- The specific whole command (operation) causing the error should be given.

54 Label file is invalid.
- The name of the label file (with full path) should be given.

55 Memory file is invalid.
- The name of the .mem file or the names of the table and memo field should be given.

56 There is not enough disk space for "name".
- The specific whole command (operation) causing the error should be given.

58 LOG( ): Zero or negative used as argument.
- The specific whole command (operation) causing the error should be given, with the value of the field/memvar involved.

61 SQRT argument cannot be negative.
- The specific whole command (operation) causing the error should be given, with the values of all fields/memvars involved.

62 Cannot access characters beyond string.
- The specific whole command (operation) causing the error should be given, with the values of all arguments involved.

67 Expression evaluator failed.
- The specific whole command (operation) causing the error should be given, with the values of all arguments involved.

78 ** or ^ domain error.
- The specific whole command (operation) causing the error should be given, with the values of all arguments involved.

91 File was not placed in memory using the LOAD command.
- The name of the file should be given.

94 Must specify additional parameters.
- The message should be changed to: "Must specify additional parameters in "name" procedure/function.

95 Statement is not allowed in interactive mode.

96 Nesting error.
- The specific whole command (operation) causing the error should be given.
-------- END of potential Wish List content ---------------------------------------------------------------------