They're now documented, as follows:

2042 Foxcode table not found, is not correct version or is incompatible. 
2043 Foxcode script "name" failure. 
2044 Textmerge is recursive. 
2045 Cannot set DBCEventFile property when DBCEvents is off. 
2046 Foxtask table is corrupted or not the correct version. 
2048 Invalid COMATTRIB value for "name" 
2049 Error loading HtmlHelp 2.0 collection. 
2050 Help for this topic/context not implemented. 
2051 Menu item's conditional statement is too long. 
2052 OrderBy clause is too long. 
2053 GroupBy clause is too long. 

>I'm in the process of designing a new general purpose error handler, and decided to programmatically generate a table contain the error number and message returned. The current documentation states that the last valid error number is 2035. However, at least in VFP 6.0 SP5, the following list of error numbers are apparently supported and appear to be connected in some cases with ADO record sets.

2036     The current Help file is empty.
>
>2038     Microsoft Visual FoxPro doesn't support and cannot
>         open this format of recordset. It contains a recordset with a shape.
>2039     Failed to create recordset.
>2040     Field mismatch.
>2041     <b>Recodset</b> does not exist.

No, folks that isn't a typo on my part. It's what MESSAGE() returns.< s >
>
>I haven't check any of the error numbers prior to 2036, so I can't comment if any new, undocumented ones exist there.