BUG: Column Name Greater Than 128 Characters Cause Error (166509)
The information in this article applies to:
- Microsoft Visual FoxPro for Macintosh 3.0b
- Microsoft Visual FoxPro for Windows 3.0
- Microsoft Visual FoxPro for Windows 3.0b
- Microsoft Visual FoxPro for Windows 6.0
This article was previously published under Q166509 SYMPTOMS
Changing a column's name to a value greater than 128 characters can cause
the operating system to return a memory violation error while modifying the
structure of the table. The error occurs after changing the column name of
a table with the ALTER TABLE command. This command allows you to
programmatically assign a column a name greater than 128 characters in
length. The dialog boxes available through the interface, such as those
invoked with the MODIFY STRUCTURE command, do not allow a name greater than
128 characters.
One of the following system error appears depending on the version of the
operating system:
- In Windows 95, the following error appears:
This program has performed an illegal operation and will be shut down.
Clicking Details reveals the following message:
VFP caused an invalid page fault in module KERNEL32.DLL
at <memory address>.
- In Windows NT 4.0, the following error appears:
An application error has occurred and an application error log is
being generated.
VFP.exe
Exception: access violation <error number>, Address: <memory address>.
- Finally, the Macintosh operating system reports:
Sorry, a system error occurred.
"Microsoft Visual FoxPro"
error type 11
In each case that error may or may not be preceded by an "Internal
consistency" error.
This error does not occur in Visual FoxPro 5.0 for Windows.
RESOLUTION
When using the ALTER TABLE command, do not create field names longer than
128 characters.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products
listed at the beginning of this article. We are researching this
bug and will post new information here in the Microsoft Knowledge
Base as it becomes available.
Modification Type: | Major | Last Reviewed: | 12/3/2003 |
---|
Keywords: | kbbug KB166509 |
---|
|