Microsoft KB Archive/113151

= PRJ: Running Recorded Macro That Selects Fields Causes Error =

Article ID: 113151

Article Last Modified on 1/18/2007

-

APPLIES TO


 * Microsoft Project 2000 Standard Edition
 * Microsoft Project 98 Standard Edition
 * Microsoft Project 4.1 Standard Edition
 * Microsoft Project 4.1a
 * Microsoft Project 4.0 Standard Edition
 * Microsoft Project 4.0 for Macintosh

-



This article was previously published under Q113151



SYMPTOMS
In Microsoft Project, when you record a macro that selects fields in a table in your project, and you have selected the Relative Row References option in the Record Macro dialog box, you may receive the following error message when you run the macro:

Run time Error '1004':

Command could not be completed successfully

-or-

Run-time error '1004':

An unexpected error occured with the method.

Check the syntax of your macro, and then try again.



CAUSE
When you record a macro that selects fields in a table, and you select the Relative Row References option in the Record Macro dialog box (the default setting), the upper left field in a selection is always considered to be the current selection. For example, if you turn the macro recorder on and select a field in row 10, and select a range up to row 1, the recorded command considers the first field in row 1 to be the active selection, though the active selection is actually a field in row 10. When you select from row 1 to row 10, the same command is recorded as when you select from row 10 to row 1.

When you have the Relative Row References option selected, this behavior causes a problem because any selection you make in a table is relative to the active selection.



WORKAROUND
To avoid this problem when you are recording a macro that selects fields in a table, do either of the following:


 * Select the Absolute (ID) Row References option in the Record Macro dialog box.

-or-


 * Always select fields in the table starting from the upper left field you want included in the selection.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

