BarcelonaJoe
New Member
- Joined
- Jan 27, 2012
- Messages
- 4
Hello Excel Experts,
I am new to the forum. Anyway, I have a hard time describing this issue so I'm not sure if it has been posted previously. If you know of a thread, please let me know.
We currently have a workbook where the users can employ selections via column filters. They would use the filters to manage their entries.
They get in trouble when they forget to reset their selections and then add a new row/s. So instead of the next true row being 255, the next row they add might start at 4834. So at times, we get frantic calls about "missing rows" or "duplicate rows" by virtue of the filter selections being on or defaulted.
We are trying to help our users by somehow detecting the filter settings and maybe using an on change event to either warn the user that the filter is being used, or do something else to make sure that the next row added after 254 is 255.
I got a year of VBA experience and 2 .XLSM 2007 workbooks in production to my name. Unfortunately, I can't seem to see a solution for this. I reason that this is a chicken and egg situation--by the time the on change event occurs, the damage has been done (meaning that the row at 4834 already exists).
Anyway, any thoughts would be appreciated.
Thanks,
BarcelonaJoe
I am new to the forum. Anyway, I have a hard time describing this issue so I'm not sure if it has been posted previously. If you know of a thread, please let me know.
We currently have a workbook where the users can employ selections via column filters. They would use the filters to manage their entries.
They get in trouble when they forget to reset their selections and then add a new row/s. So instead of the next true row being 255, the next row they add might start at 4834. So at times, we get frantic calls about "missing rows" or "duplicate rows" by virtue of the filter selections being on or defaulted.
We are trying to help our users by somehow detecting the filter settings and maybe using an on change event to either warn the user that the filter is being used, or do something else to make sure that the next row added after 254 is 255.
I got a year of VBA experience and 2 .XLSM 2007 workbooks in production to my name. Unfortunately, I can't seem to see a solution for this. I reason that this is a chicken and egg situation--by the time the on change event occurs, the damage has been done (meaning that the row at 4834 already exists).
Anyway, any thoughts would be appreciated.
Thanks,
BarcelonaJoe