Home |
Search |
Today's Posts |
#9
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Good point about possibility of a Shared workbook being linked to
unexpectedly long row deletion time (though a lot of rows can take a while in some scenarios). The Delete button could indeed be removed and replaced with an alternative. Though easier to intercept it's click event, trap the current selection (ie rows) to process later, could abort the Delete button's click event and go on from there (downside is Undo is lost). It's a more difficult to intercept what user does when Deleting from the Cell's right click popup Regards, Peter T "GB" wrote in message ... Considering that this seems like an application that may be desirable to be openable by many people at once, is the workbook shared, and if so is it possible that when the user uses either the menu command delete rows or highlights these rows and right clicks to delete, that all of the data is being captured in the "changes"? BTW, in rewriting the Row-Delete menu item, curious about plan of attack. Will you be removing the default option from the menu bar and adding your own code to it, or using some form of VBA override code that is called by Excel in lieu of the default Row-Delete? "Nick H" wrote: Thanks Peter, You're absolutely right, I have encountered the 424 error when trying to process objects that had passed the 'Not Nothing' test. On Error Resume Next currently gets me round the issue because in all places where it occurs the next line is destroying the object anyway. At the moment I cater for the 'odd' deletion/insertion of rows by tearing down and rebuilding all the portfolio objects if I detect a change in the row count. Even with 1200 rows of data this takes only a second so I felt it a small price for playing safe. While experimenting I've found that if I manually run my 'KillPortfolio' routine (tear down) and then select 600+ portfolio rows for deletion, the delete happens virtually instantaneously. I can then 'RebuildPortfolio' in the Factory module and all's well. I realise I've solved my own problem in that I simply need to control the deletion by rewriting the "Row" 'Delete' menu item - Teardown portfolio, do the delete, Rebuild portfolio - but I feel unfulfilled. I just wish I knew what Excel is doing during that 30 second lull and would it be avoidable if I was a better programmer? What I don't want to do is turn it into a dictator app that forces the user to conform to non-Excel like ways. Br, Nick H |