Name 

Description 

Data Breakpoint is set on a stack location 

Stack memory is volatile and changes a lot. When a data breakpoint is set on an address in the stack, the breakpoint might be hit quite often, each time something is pushed on or popped off the stack.
You can still set this breakpoint, but be aware that it might get hit so often that the application cannot run properly. 

Misaligned Data Breakpoint 

You attempted to set a data breakpoint whose Address is misaligned with respect to its Length.
If the data breakpoint has a two-byte length, then the Address should be aligned on a two-byte boundary. Similarly, the Address of a four-byte data breakpoint should be aligned on a four-byte boundary.
You can still set this data breakpoint, but if you do, the breakpoint will be set on an address that is on an appropriate boundary. This can trigger the breakpoint in unintended situations. 

Error address not found 

The address you have specified cannot be mapped to a source code position. This error usually occurs for one of the following reasons:

• The address you entered is invalid or is not an address in your application.
• The module containing the specified address was not compiled with debug information.
• The address specified does not correspond to a program statement.

Note that the runtime and visual component libraries are compiled without debug information. 

Another file named <FileName> is already on the search path 

A file with the same name as the one you just specified is already in another directory on the search path. 

Could not stop due to hard mode 

The integrated debugger has detected that Windows is in a modal state and will not allow the debugger to stop your application. Windows enters "hard mode" whenever processing an inter-task SendMessage, when there is no task queue, or when the menu system is active. You will not generally encounter hard mode unless you are debugging DDE or OLE processes within Delphi.
A standalone debugger such as the Turbo Debugger for Windows can be used to debug applications even when Windows is in hard mode. 

Error creating process: <Process> (<ErrorCode>) 

Delphi was unable to start your application for the reason specified.
For more information about "Insufficient memory to run" errors, see the README.TXT file. 

A component class named <name> already exists 

A package with the name you specified is already installed in the IDE. Rename the package or check if the package you are trying to install is already there. 

A field or method named <name> already exists 

The name you have specified is already being used by an existing method or field.
For a complete list of all fields and methods defined, check the form declaration at the top of the unit source file. 

The project already contains a form or module named <Name> 

Every module name (program or library, form, and unit) in a project must be unique. 

Incorrect field declaration in class <ClassName> 

In order to keep your form and source code synchronized, Delphi must be able to find and maintain the declaration of each field in the first section of the form's class definition. Though the compiler allows more complex syntax, the form Designer will report an error unless each field that is declared in this section is equivalent to the following:  

Field <Field Name> does not have a corresponding component. Remove the declaration? 

The first section of your form's class declaration defines a field for which there is no corresponding component on the form. Note that this section is reserved for use by the form Designer.
To declare your own fields and methods, place them in a separate public, private, or protected section.
This error will also occur if you load the binary form file (.DFM) into the Code editor and delete or rename one or more components. 

Field <Field Name> should be of type <Type1> but is declared as <Type2>. Correct the declaration? 

The type of specified field does not match its corresponding component on the form. This error will occur if you change the field declaration in the Code editor or load the binary form file (.DFM) into the Code editor and modify the type of a component.
If you select No and run your application, an error will occur when the form is loaded. 

Declaration of class <ClassName> is missing or incorrect 

Delphi is unable to locate the form's class declaration in the interface section of the unit. This is probably because the type declaration containing the class has been deleted, commented out, or incorrectly modified. This error will occur if Delphi cannot locate a class declaration equivalent to the following:  

Module header is missing or incorrect 

The module header has been deleted, commented out, or otherwise incorrectly modified. Use UNDO to reverse your changes, or correct the declaration manually.
In order to keep your form and source code synchronized, Delphi must be able to find a valid module header at the beginning of the source file. A valid module header consists of the reserved word unit, program or library, followed by an identifier (for example, Unit1, Project1), followed by a semi-colon. The file name must match the identifier.
For example, Delphi will look for a unit named Unit1 in UNIT1.PAS, a project named Project1 in PROJECT1.DPR,... more 

IMPLEMENTATION part is missing or incorrect 

In order to keep your form and source code synchronized, Delphi must be able to find the unit's implementation section. This reserved word has been deleted, commented out, or misspelled.
Use UNDO to reverse your changes or correct the reserved word manually. 

Insufficient memory to run 

Delphi was unable to run your application due to insufficient memory or Windows resources. Close other Windows applications and try again.
This error sometimes occurs because of insufficient low (conventional) memory. For further information, see the README.TXT file. 

Breakpoint is set on line that contains no code or debug information. Run anyway? 

A breakpoint is set on a line that does not generate code or in a module which is not part of the project. If you choose to run anyway, invalid breakpoints will be disabled (ignored). 

<IDname> is not a valid identifier 

The identifier name is invalid. Ensure that the first character is a letter or an underscore (_). The characters that follow must be letters, digits, or underscores, and there cannot be any spaces in the identifier. 

<Library Name>is already loaded, probably as a result of an incorrect program termination. Your system may be unstable and you should exit and restart Windows now. 

An error occurred while attempting to initialize Delphi's component library. One or more DLLs are already in memory, probably as a result of an incorrect program termination in a previous Delphi or BDE session.
You should exit and then restart Windows. 

Incorrect method declaration in class <ClassName> 

In order to keep your form and source code synchronized, Delphi must be able to find and maintain the declaration of each method in the first section of the form's class definition. The form Designer will report an error unless the field and method declarations in this section are equivalent to the following:  

Cannot find implementation of method <MethodName> 

The indicated method is declared in the form's class declaration but cannot be located in the implementation section of the unit. It probably has been deleted, commented out, renamed, or incorrectly modified.
Use UNDO to reverse your changes, or correct the procedure declaration manually. Be sure the declaration in the class is identical to the one in the implementation section. (This is done automatically if you use the Object Inspector to create and rename event handlers.) 

The <Method Name> method referenced by <Form Name>.<Event Name> has an incompatible parameter list. Remove the reference? 

A form has been loaded that contains an event property mapped to a method with an incompatible parameter list. Parameter lists are incompatible if the number or types of parameters are not identical.
For a list of methods declared in this form which are compatible for this event property, use the dropdown list on the Object Inspector's Events page.
This error occurs when you manually modify a method declaration that is referenced by an event property.
Note that it is unsafe to run this program without removing the reference or correcting the error. 

The <Method Name> method referenced by <Form Name> does not exist. Remove the reference? 

The indicated method is no longer present in the class declaration of the form. This error occurs when you manually delete or rename a method in the form's class declaration that is assigned to an event property.
If you select No and run this application, an error will occur when the form is loaded. 

No code was generated for the current line 

You are attempting to run to the cursor position, but you have specified a line that did not generate code, or is in a module which is not part of the project.
Specify another line and try again.
Note that the smart linker will remove procedures that are declared but not called by the program (unless they are virtual method of an object that is linked in). 

Property and method <MethodName> are not compatible 

You are assigning a method to an event property even though they have incompatible parameter lists. Parameter lists are incompatible if the number of types of parameters are not identical. For a list of compatible methods in this form, see the dropdown list on the Object Inspector Events page. 

Cannot find <FileName.PAS> or <FileName.DCU> on the current search path 

The .pas or .dcu file you just specified cannot be found on the search path.
You can modify the search path, copy the file to a directory along the path, or remove the file from the list of installed units. 

Source has been modified. Rebuild? 

You have made changes to one or more source or form modules while your application is running. When possible, you should terminate your application normally (select No, switch to your running application, and select Close on the System Menu), and then run or compile again.
If you select Yes, your application will be terminated and then recompiled. 

Symbol <BrowseSymbol> not found. 

The browser cannot find the specified symbol. This error occurs if you enter an invalid symbol name or if debug information is not available for the module that contains the specified symbol. 

Debug session in progress. Terminate? 

Your application is running and will be terminated if you proceed. When possible, you should cancel this dialog and terminate your application normally (for example, by selecting Close on the System Menu). 

Uses clause is missing or incorrect 

In order to keep your forms and source code synchronized, Delphi must be able to find and maintain the uses clause of each module.
In a unit, a valid uses clause must be present immediately following the interface reserved word. In a program or library, a valid uses clause must be present immediately following the program or library header.
This error occurs because the uses clause has been deleted, commented out, or incorrectly modified. Use undo to reverse your changes or correct the declaration manually. 

Invalid event profile <Name> 

The VBX control you are installing is invalid.