> Does this problem occur only when calc mode is automatic? If so and if you
> have any UDFs it might be an interaction with them.
[quoted text clipped - 30 lines]
> |
> | Any help anyone can provide is greatly appreciated.
I am not doing anything special, just a simple new excel workbook. I
have never set calc mode so it is still what it is defaulted to from
the base installation.
There are no other user defined functions firing, I believe that to be
true for two reasons. One it is a new blank workbook and I have
defined none. Two, the subroutine aborts execution right after I set
the value of the cell. Isn't VBA an event driven procedural language?
meaning that two events cant really fire at the exact same time? When
this subroutine fails it is if it is executing the statement "exit
sub", at least as far as the debugger shows.
I tried to do a simple test to see if it was exiting the subroutine or
just crashing with no error. I took and made a simple subroutine and
then called the offending subroutine. If the subroutine was exiting
gracefully then the next statement after the call function would be
executed. (see code)
Private Sub CommandButton1_Click()
MsgBox "Calling Subroutine"
Call test
MsgBox "Completed Subroutine"
End Sub
Private Sub test()
Sheets("Sheet1").Cells(11, 10).Value = 54321
Sheets("Sheet1").Cells(12, 10).Value = 12345
End Sub
When I ran this I only got the first msgbox, so what ever is
interrupting the code is failing after the first statement in the
test() subroutine: Sheets("Sheet1").Cells(11, 10).Value = 54321.
Dave Peterson - 27 Mar 2008 23:26 GMT
And if you create a small test workbook with just enough info to test your
routine, does it work ok?
> > Does this problem occur only when calc mode is automatic? If so and if you
> > have any UDFs it might be an interaction with them.
[quoted text clipped - 63 lines]
> interrupting the code is failing after the first statement in the
> test() subroutine: Sheets("Sheet1").Cells(11, 10).Value = 54321.

Signature
Dave Peterson
Jim Rech - 28 Mar 2008 16:01 GMT
>>One it is a new blank workbook
That rules out my idea.
One thing I would try is starting Excel in safe mode just to be sure no
add-in or something else is involved.
From Start->Run run "Excel.exe /s" (no quotes, there is a space before the
slash). Then try your code.

Signature
Jim
>> Does this problem occur only when calc mode is automatic? If so and if
>> you
[quoted text clipped - 64 lines]
> interrupting the code is failing after the first statement in the
> test() subroutine: Sheets("Sheet1").Cells(11, 10).Value = 54321.
beau.moore@gmail.com - 28 Mar 2008 20:44 GMT
When I tried safe mode it worked, but it prompted me to enable active
x controls. It is good that it worked but now I need to find out why
it does work in normal mode.
Jim Rech - 28 Mar 2008 22:06 GMT
So the next step is to find what workbook or add-in that loads with Excel is
causing the problem. You should look at Add-ins under Excel Options on the
Office button menu. If you see any add-ins loading there you could unload
them all or one at a time and test your macro. Also look in your XLSTART
folder(s). Most anything there loads with Excel also. You could move them
out (with Excel closed) and test your macro.

Signature
Jim
> When I tried safe mode it worked, but it prompted me to enable active
> x controls. It is good that it worked but now I need to find out why
> it does work in normal mode.