Many of these problems seem to be less prevalent with later versions (the above conditions caused them repeatedly with xl97) - conditions 1 and 2 have caused me problems here at work on xl2003.
There is a bug which leavs the 'Forms' toolbar floating when switching from worksheet view to VBE view, and saving when this happens invariably corrupts the workbook. Many times when I've tried it with later versions as I've progressed through the versions, I've expected this problem to be resolved, but the same thing has happened time and time again, regardless. And this is on different types of PC, using different types of network software (Novell and NT Server, various versions) and at home with no network.
BizMark
Quote:
|
Originally Posted by Dave Peterson
I've gotten that error (one or two times vbg). But none that I could
attribute to an "on error resume next" line.
#2. I use xl2003 and don't use many dialog sheets, but I almost always have the
forms toolbar, drawing toolbar, and control toolbox toolbar visible. As a test,
I added a dialog sheet and then swapped to the VBE. Nothing bad happened.
#3. I don't recall ever having excel crash when I had range names that had
errors. (My code crashed--but not excel.
#4. I've never seen excel crash because of this, either.
I've found that excel crashes with I do something wrong with an API function or
maybe even a corrupt workbook. Or other things that I couldn't pinpoint
(non-reproducible types).
BizMark wrote:
Dave Peterson Wrote:
I'm not sure what error you're writing about (in xl97),
I think millions of Excel users around the world are only too aware
what error message this is.
Surely you can't tell me you've NEVER had this?
"Microsoft Excel has performed an Illegal Operation and will be shut
down. If the problem persists, please contact the software vendor".
Or, in later versions,
"Microsoft Excel has encountered a problem and needs to close. We
apologise for any inconvenience. Do you want to submit an error
report?"
There are a myriad causes for this behaviour, some are consistently
repeatable and therefore trappable, and some are not. Any situation
which causes these to happen with any regularity, it is useful to
people to point out as it can prevent them from losing many man hours
or days of work. Some a
1. Using On Error Resume Next then On Error Goto 0
2. Editing VBA code when the 'Forms' toolbar was open on a Dialogsheet
before switching to the VBE, then saving in the VBE
3. Operating on range names in macros when the name definitions contain
#REFs etc.
4. One user running macro in a workbook, another user having the same
workbook open as Read-Only, then the other user does 'Save As' to make
a copy - result - Illegal Operation/Encountered a Problem error occurs
for user running the macros.
There are many others that don't spring to mind straight away.
Sometimes this error cannot be explained.
However, I think StinkeyPete needs to realise that it needn't be an
issue just because somebody has issued a warning over his solution.
BizMark
--
BizMark
--
Dave Peterson
|