Oh good a trivial argument... you get so few of these on USENET :-) I'm
with Armin on this. If adding part of the variable's type definition onto
the variable name is a good idea then clearly syntax such as the following
would tell us that MyObject is a reference "before" having to see what it is
a reference to.
Dim MyObject* As Form
And as Armin intimates, if an IntegerArray keyword was defined nobody would
be questioning this at all.
Also Armin didn't actually "schrieb" what is stated in Herfried's reply.
The "One is correct and the other isn't

" quote was written by "Ray
Cassick" <rcassickNO-(E-Mail Removed)> and while I note the grin in his
reply I will suggest that he is correct, he simply selected the wrong
example as the correct one :-) What you have is reference to an integer
array so why not declare it as such?
"Herfried K. Wagner [MVP]" <hirf-spam-me-(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> "Armin Zingler" <(E-Mail Removed)> schrieb:
>>> One is correct and the other isn't 
>>>
>>> Dim MyArray() As Integer = {5, 7, 8, 9, 0} says exactly what you
>>> want. You want an array of integer types.
>>>
>>> Dim MyArray As Integer() = {5, 7, 8, 9, 0} really says that you want
>>> a reference to an integer array.
>>>
>>> While both will compile the second is a very ambiguous way to state
>>> what you want.
>>
>> The type of the variable is "integer array". The "()" (read: array) are
>> part
>> of the type name. The variable type is put after the "As" keyword.
>> Consequently "As Integer()" (read: As Integer Array) makes more sense.
>
> Well, I think that both declarations make sense, and I prefer the 'Dim
> MyArray() As Integer' declaration for readability reasons (I think it's
> more important that a variable contains an array than to read the type of
> its items first).