Microsoft could make error checking a lot easier, even possible in some
cases, it you would add the following to VBA:

1) Provide a function similar to UBound() and obj.Rows.Count that would work
on either Excel Range objects as arguments to Function Procedures, and
2) a function, call it Static2 for which a Static2 variable passes out of
existance when a VBA procedure returns control to Excel, or
3) a function, call it IsRangeObject, that can be used to test if an
argument to a VBA procedure is an Excel Range Object, as opposed to a VBA
array.

You coud use it in Excel, for example, instead of a #Value error, to tell
the user in a MsgBox that in the function MMult(x,y) the array x must have
the same number of columns as Y has rows. In the applications I write, or
would like to write but can't" this capability is very desirable or sometimes
aessential.

Thanks
--
Thanks for your help

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...el.programming