Jagged arrays - Cannot Define with Arr1()() as integer = New integ
 

On MS site, it says use the following to define Jagged arrays:
Arr1()() as Double = New Double()() {}
how come it doesn't seem to work in Excel's VB?

Jagged arrays - Cannot Define with Arr1()() as integer = New integ
 

Post the URL for this citation.

Is it for VB6? To the best of my knowledge, VB6 doesn't use any notation
like that.

If it isn't about VB6, then there's your huckleberry.

--
Regards,
Tom Ogilvy


"J@Y" wrote:

On MS site, it says use the following to define Jagged arrays:
Arr1()() as Double = New Double()() {}
how come it doesn't seem to work in Excel's VB?

Jagged arrays - Cannot Define with Arr1()() as integer = New i
 

Its under visual studio
http://msdn2.microsoft.com/en-us/lib...9t(VS.80).aspx


"Tom Ogilvy" wrote:

Post the URL for this citation.

Is it for VB6? To the best of my knowledge, VB6 doesn't use any notation
like that.

If it isn't about VB6, then there's your huckleberry.

--
Regards,
Tom Ogilvy


"J@Y" wrote:

On MS site, it says use the following to define Jagged arrays:
Arr1()() as Double = New Double()() {}
how come it doesn't seem to work in Excel's VB?

Jagged arrays - Cannot Define with Arr1()() as integer = New i
 

The page clearly states -

"This page is specific to
Microsoft Visual Studio 2005/.NET Framework 2.0"

which is not VB/VBA and makes Tom's huckleberry comment highly apposite.

But I can see why you may have been misled into thinking otherwise when the
page is also titled "Visual Basic Language Concepts".

Regards,
Peter T

"J@Y" wrote in message
...
Its under visual studio
http://msdn2.microsoft.com/en-us/lib...9t(VS.80).aspx


"Tom Ogilvy" wrote:

Post the URL for this citation.

Is it for VB6? To the best of my knowledge, VB6 doesn't use any
notation
like that.

If it isn't about VB6, then there's your huckleberry.

--
Regards,
Tom Ogilvy


"J@Y" wrote:

On MS site, it says use the following to define Jagged arrays:
Arr1()() as Double = New Double()() {}
how come it doesn't seem to work in Excel's VB?

Jagged arrays - Cannot Define with Arr1()() as integer = New integ
 

As others have pointed out, that is not VB/VBA code.
Something like this maybe:

Private Sub CommandButton1_Click()
Dim arrAll As Variant
Dim i As Long
Dim TempStr As String

Const MAX_ENTRIES As Long = 10

ReDim arrAll(1 To MAX_ENTRIES)

For i = 1 To MAX_ENTRIES
TempStr = Application.WorksheetFunction.Rept("Text,", Rnd() * 50)
arrAll(i) = Split(TempStr, ",")
Next

Dim j As Long

For i = LBound(arrAll) To UBound(arrAll)
For j = LBound(arrAll(i)) To UBound(arrAll(i))
Debug.Print i, j, arrAll(i)(j)
Next 'j
Next 'i

End Sub

NickHK

"J@Y" wrote in message
...
On MS site, it says use the following to define Jagged arrays:
Arr1()() as Double = New Double()() {}
how come it doesn't seem to work in Excel's VB?

Jagged arrays - Cannot Define with Arr1()() as integer = New i
 

Peter,
Whilst you are correct in this instance, it would seem MS are putting
similar statements on all pages, whether applicable or not. See:
http://msdn2.microsoft.com/en-us/library/aa384106.aspx

Just to add to the confusion....

NickHK

"Peter T" <peter_t@discussions wrote in message
...
The page clearly states -

"This page is specific to
Microsoft Visual Studio 2005/.NET Framework 2.0"

which is not VB/VBA and makes Tom's huckleberry comment highly apposite.

But I can see why you may have been misled into thinking otherwise when
the
page is also titled "Visual Basic Language Concepts".

Regards,
Peter T

"J@Y" wrote in message
...
Its under visual studio
http://msdn2.microsoft.com/en-us/lib...9t(VS.80).aspx


"Tom Ogilvy" wrote:

Post the URL for this citation.

Is it for VB6? To the best of my knowledge, VB6 doesn't use any
notation
like that.

If it isn't about VB6, then there's your huckleberry.

--
Regards,
Tom Ogilvy


"J@Y" wrote:

On MS site, it says use the following to define Jagged arrays:
Arr1()() as Double = New Double()() {}
how come it doesn't seem to work in Excel's VB?

Jagged arrays - Cannot Define with Arr1()() as integer = New i
 

Hi Nick,

Seems they forgot to change the sign on the door !

Regards,
Peter T

"NickHK" wrote in message
Peter,
Whilst you are correct in this instance, it would seem MS are putting
similar statements on all pages, whether applicable or not. See:
http://msdn2.microsoft.com/en-us/library/aa384106.aspx

Just to add to the confusion....

NickHK
<snip