The Excel VBO is really just a wrapper for the Excel VBA API, so technically anything that can be done via an Excel macro (VBA) can be done by a BP code stage (.Net). As you can imagine, the scope of the Excel API is vast, and so the BP object only covers the essential part of it. The functionality you describe does not exist in the object but it could be added with some programming ability. I find the easiest way is to first record a macro and examine the resulting macro code. This code can't be pasted into BP, but it is useful in guiding the programmer into creating the equivalent .Net code.
