VBA Variable Display

[Eric]

when running in debug mode I was able to see the variable values by
putting the cursor over the variable in office 2000 for the PC. How do
I get this function to work on office X for the Mac?

for i= 1 to 10
test(i)=
next i

In this example putting the cursor over either test or (i) would give
me the value of the figure going into test and putting the cursor over
i would give me the value i is.

Thanks

 

[JE McGimpsey]

when running in debug mode I was able to see the variable values by
putting the cursor over the variable in office 2000 for the PC. How do
I get this function to work on office X for the Mac?

for i= 1 to 10
test(i)=
next i

In this example putting the cursor over either test or (i) would give
me the value of the figure going into test and putting the cursor over
i would give me the value i is.

You can't - MacXL's VBE doesn't have this feature (nor intellisense, a
Watch window, etc.)

Instead, use

? i

in the immediate window, or put

Debug.Print i

in-line in the code.

 

[Eric]

Thanks for the information. Are they going to change this in an
upcoming patch or is this how Mac users like it?

 

[JE McGimpsey]

Thanks for the information. Are they going to change this in an
upcoming patch or is this how Mac users like it?

No and no.

However, some Mac developers (like me) are used to it, so don't miss the
bells and whistles. We content ourselves that our coding is more formal
and our understanding of methods and properties is greater because we
don't have the props that Win users do.

However, VBA is a dead language walking. It will be supported in the
future, but no further development will occur on either platform, and
certainly not the VBE. The money can be much better spent on other
features.

We can hope that the next Office IDE (i.,e., implementing .Not) will be
able to be ported more fully.

 

[Bob Greenblatt]

No and no.

However, some Mac developers (like me) are used to it, so don't miss the
bells and whistles. We content ourselves that our coding is more formal
and our understanding of methods and properties is greater because we
don't have the props that Win users do.

However, VBA is a dead language walking. It will be supported in the
future, but no further development will occur on either platform, and
certainly not the VBE. The money can be much better spent on other
features.

We can hope that the next Office IDE (i.,e., implementing .Not) will be
able to be ported more fully.

Was ".not" a Freudian slip?

 

[JE McGimpsey]

Was ".not" a Freudian slip?

..Nope

<g>