cmerch19602006
Programmer
Hey folks! I am new here, and really did try searching the threads, but I bet you all know how that can go sometimes.
I am building a project planner in Excel 2003 (I don't like any of the one's I've seen). I want to automatically reposition previous entries when new entries are entered into a sheet. I attempted this by using a "worksheet_change" macro that inserts a new row, then moves the new entry into that row.
A lot of you probably already know what happened with that, but I'll describe it anyway:
Because the macro is activated by a change in the worksheet, and the macro also causes a changes in the worksheet, the changes cause the macro to run again. Endless process!
My question:
Is there a way to cause the Worksheet_Change macro to stop it's own reactivation by, say, turning off all auto macro operations temporarily?
There is code in VBA help to turn off the AutomationSecurity and then turn it back on but it doesn't work for this purpose.
I have considered switching to a userform for input but I thought using the Worsheet_Change would be more efficient and require a lot less code.
I am building a project planner in Excel 2003 (I don't like any of the one's I've seen). I want to automatically reposition previous entries when new entries are entered into a sheet. I attempted this by using a "worksheet_change" macro that inserts a new row, then moves the new entry into that row.
A lot of you probably already know what happened with that, but I'll describe it anyway:
Because the macro is activated by a change in the worksheet, and the macro also causes a changes in the worksheet, the changes cause the macro to run again. Endless process!
My question:
Is there a way to cause the Worksheet_Change macro to stop it's own reactivation by, say, turning off all auto macro operations temporarily?
There is code in VBA help to turn off the AutomationSecurity and then turn it back on but it doesn't work for this purpose.
I have considered switching to a userform for input but I thought using the Worsheet_Change would be more efficient and require a lot less code.