[VBA] Something like COUNTIFS for Excel 2003

Well, there you go. A colleague sends you a copy of an Excel file and needs a nice formula. So I do the nice formula. Then I try to save the sheet back into the same form in which it arrived:

Clang!

Seems that Excel 2003 doesn't have the nice little COUNTIFS function that I have in my Excel 2007. What to do, what to do, what to do ...

Well, it'd be nice to install Office 07, but in the interim, how about a bit of VBA?

We'll call it RANGEDCOUNT, and it will accept a range of data, and a string being the criteria. The criteria can be

1. a single value preceded by an operation (>, >=, =, <=, <, #), or


2. a range of values, the upper and lower bounds separated by a dash.

Function RANGEDCOUNT(rData As Range, rCriteria As String) As Integer
        Dim i As Long
        Dim sOper As String
        Dim dAmt As Double
        Dim dUpper As Double
        Dim dLower As Double
        Dim bRanged As Boolean
        Dim iDash As Integer
        Dim dDataItem As Double
        Dim iCount As Integer
        iCount = 0
        bRanged = False

Right, that's all the declarations over with. Now to check whether we have a range specification or not and what to do if it's not. Notice the 'Instr(2' which checks for an equals sign after the first character, as we're checking to see if we have '>=' or '<=' and don't want to fail on a bare equals

        iDash = InStr(1, rCriteria, "-")
        If iDash = 0 Then
                If InStr(2, rCriteria, "=") Then
                        sOper = Left$(rCriteria, 2)
                        dAmt = Val(Mid$(rCriteria, 3))
                Else
                        sOper = Left$(rCriteria, 1)
                        dAmt = Val(Mid$(rCriteria, 2))
                End If

The else fires if we do in fact have a range setting and handles that appropriately.

        Else
                bRanged = True
                dLower = Val(Left$(rCriteria, iDash - 1))
                dUpper = Val(Mid$(rCriteria, iDash + 1))
        End If

Next, step through the data and for each element, apply the logic for either a ranged count or an operator count.

        For i = 1 To rData.Count '- 1 'LBound(rData.) To UBound(rData)
                dDataItem = rData(i).Value
                If bRanged Then
                        If dDataItem >= dLower And dDataItem <= dUpper Then
                                iCount = iCount + 1
                        End If
                Else
                        Select Case sOper
                        Case "="
                                If dDataItem = dAmt Then iCount = iCount + 1
                        Case "<"
                                If dDataItem < dAmt Then iCount = iCount + 1
                        Case ">"
                                If dDataItem > dAmt Then iCount = iCount + 1
                        Case "<="
                                If dDataItem <= dAmt Then iCount = iCount + 1
                        Case ">="
                                If dDataItem >= dAmt Then iCount = iCount + 1
                        Case "#"
                                If dDataItem <> dAmt Then iCount = iCount + 1
                        End Select
                End If
        Next

Okay, iCount should have the result, so put it in RANGEDCOUNT and end.

        RANGEDCOUNT = iCount
End Function

Not bad for 15 to 20 minutes work, and would've been faster if I'd remembered how to get data out of Ranges. Now my colleague is happier and I've had a chance to do some something interesting. Granted, it's not particularly fault tolerant, but it's enough for now. © Bruce M. Axtens, 2010

[Visual BASIC 6] BOOST (v2)

I revisited BOOST this week. A friend had pointed out to me some time back that /P: and /L: were a bit of a pain when one wanted to speed something up quickly, or kill it quickly. So this version changes the command line handling.

This version also demonstrates how to kill a process. In fact it kills every process of the same name. I wish I'd had this a couple of years ago when I was doing stuff with Excel -- I'd end up with multiple Excel sessions which I would then have to kill off one-by-one through the Task Manager. (I eventually ended up installing Cygwin so that I could script the process.)

If you remember the original VBScript of BOOST and the first VB6 version, you'll see some similarities.

I've given up on using setsubsys in favour of using VBAdvance (which is now freeware) to handle the compile-to-console-app process. I'm still compressing the app using UPX.

First a few constants and the declarations, found on vb.mvps.org, for doing console I/O.

Option Explicit Const KILL_PROCESS = 0 '0 Const LOW_PRIORITY = 64 '1 Const BELOWNORMAL_PRIORITY = 16384 '2 Const NORMAL_PRIORITY = 32 '3 Const ABOVENORMAL_PRIORITY = 32768 '4 Const HIGH_PRIORITY = 256 '5 Const REALTIME_PRIORITY = 128 '6 Private Declare Function GetStdOutHandle Lib "kernel32" _ Alias "GetStdHandle" _ (Optional ByVal HandleType As Long = -11) As Long Private Declare Function WriteFile Lib "kernel32" _ (ByVal hFile As Long, _ ByVal lpBuffer As String, _ ByVal cToWrite As Long, _ ByRef cWritten As Long, _ Optional ByVal lpOverlapped As Long) As Long 'To keep things simple, wrap these two APIs in a single helper function like so: Private Function ConsoleWrite(sText As String) As Long WriteFile GetStdOutHandle, ByVal sText, Len(sText), ConsoleWrite End Function

Next, a few supporting functions. First off the rank, is an invocation syntax display. Notice that priority can now be specified either by a number (0 to kill, 1-6 for low to realtime) or by name (kill, low, belownormal, normal, abovenormal, high, realtime).

Sub Syntax() ConsoleWrite ("Syntax:" & vbNewLine & _ vbTab & "Boost {processname} {runlevel}" & vbNewLine & _ "Run level as number:" & vbNewLine & _ vbTab & "0 = KILL_PROCESS" & vbNewLine & _ vbTab & "1 = LOW_PRIORITY" & vbNewLine & _ vbTab & "2 = BELOWNORMAL_PRIORITY" & vbNewLine & _ vbTab & "3 = NORMAL_PRIORITY" & vbNewLine & _ vbTab & "4 = ABOVENORMAL_PRIORITY" & vbNewLine & _ vbTab & "5 = HIGH_PRIORITY" & vbNewLine & _ vbTab & "6 = REALTIME_PRIORITY" & vbNewLine & vbNewLine & vbNewLine & _ "Run level as text:" & vbNewLine & _ vbTab & "kill = KILL_PROCESS" & vbNewLine & _ vbTab & "low = LOW_PRIORITY" & vbNewLine & _ vbTab & "belownormal = BELOWNORMAL_PRIORITY" & vbNewLine & _ vbTab & "normal = NORMAL_PRIORITY" & vbNewLine & _ vbTab & "abovenormal = ABOVENORMAL_PRIORITY" & vbNewLine & _ vbTab & "high = HIGH_PRIORITY" & vbNewLine & _ vbTab & "realtime = REALTIME_PRIORITY" & vbNewLine) End Sub

Second, the command line parser. This splits on space and tab and is based on code found at microsoft.public.vb.winapi

Function GetCommandLine(Optional MaxArgs) As Variant 'Declare variables. Dim C As String Dim CmdLine As String Dim CmdLnLen As Integer Dim InArg As Boolean Dim i As Integer Dim NumArgs As Integer Dim ArgArray As Variant 'See if MaxArgs was provided. If IsMissing(MaxArgs) Then MaxArgs = 10 'Make array of the correct size. ReDim ArgArray(MaxArgs - 1) NumArgs = 0: InArg = False 'Get command line arguments. CmdLine = Command() CmdLnLen = Len(CmdLine) 'Go thru command line one character 'at a time. For i = 1 To CmdLnLen C = Mid(CmdLine, i, 1) 'Test for space or tab. If (C <> " " And C <> vbTab) Then 'Neither space nor tab. 'Test if already in argument. If Not InArg Then 'New argument begins. 'Test for too many arguments. If NumArgs = MaxArgs Then Exit For NumArgs = NumArgs + 1 InArg = True End If 'Concatenate character to current argument. ArgArray(NumArgs - 1) = ArgArray(NumArgs - 1) & C Else 'Found a space or tab. 'Set InArg flag to False. InArg = False End If Next i 'Resize array just enough to hold arguments. ReDim Preserve ArgArray(NumArgs - 1) 'Return Array in Function name. GetCommandLine = ArgArray '() End Function

Third, the two routines which wrap the WMI functions to set priority and to kill process. The latter was found at tek-tips. If I remember correctly, the places in each routine where it says

sComputer = "."

could, in fact, have some other computer's name. If you had sufficient privilege you could be tweaking or killing a process on someone else's machine.

Function SetPriority(sProcess As String, nPriority As Integer) As Boolean Dim sComputer As String Dim oWMIService As Object Dim cProcesses As Object Dim oProcess As Object Dim bDone As Boolean bDone = False sComputer = "." Set oWMIService = GetObject("winmgmts:\\" & sComputer & "\root\cimv2") On Error Resume Next Set cProcesses = oWMIService.ExecQuery _ ("Select * from Win32_Process Where Name = '" & sProcess & "'") For Each oProcess In cProcesses oProcess.SetPriority (nPriority) If Err.Number <> 0 Then GoTo DoNext End If bDone = True DoNext: Next On Error GoTo 0 SetPriority = bDone End Function Function KillProcess(sProcess As String) As Integer Dim oWMIService As Object Dim sComputer As String Dim oProcess As Object Dim nDone As Integer nDone = 0 sComputer = "." 'this computer Set oWMIService = GetObject("winmgmts:") For Each oProcess In oWMIService.InstancesOf("Win32_process") If LCase(oProcess.Name) = LCase(sProcess) Then oProcess.Terminate nDone = nDone + 1 End If Next KillProcess = nDone End Function

Finally, the Main subroutine. Notice the additions to the priorities collection. Note also the change in the way the command line is handled.

Because there's no .Exists method on Collections, the .Item call is wrapped in an 'On Error' so that a non-existent item situation is caught appropriately.

Sub Main() Dim sLevel As String Dim nLevel As Integer Dim sProcess As String Dim sCommand As String Dim nInstances As Integer Dim dPriorities As New Collection dPriorities.Add Item:=KILL_PROCESS, Key:="kill" dPriorities.Add Item:=LOW_PRIORITY, Key:="low" dPriorities.Add Item:=BELOWNORMAL_PRIORITY, Key:="belownormal" dPriorities.Add Item:=NORMAL_PRIORITY, Key:="normal" dPriorities.Add Item:=ABOVENORMAL_PRIORITY, Key:="abovenormal" dPriorities.Add Item:=HIGH_PRIORITY, Key:="high" dPriorities.Add Item:=REALTIME_PRIORITY, Key:="realtime" dPriorities.Add Item:=KILL_PROCESS, Key:="0" dPriorities.Add Item:=LOW_PRIORITY, Key:="1" dPriorities.Add Item:=BELOWNORMAL_PRIORITY, Key:="2" dPriorities.Add Item:=NORMAL_PRIORITY, Key:="3" dPriorities.Add Item:=ABOVENORMAL_PRIORITY, Key:="4" dPriorities.Add Item:=HIGH_PRIORITY, Key:="5" dPriorities.Add Item:=REALTIME_PRIORITY, Key:="6" Dim aArgs As Variant If Command() = "" Then Syntax End End If aArgs = GetCommandLine(2) sProcess = aArgs(0) sLevel = aArgs(1) If sProcess = "" Or sLevel = "" Then Syntax End End If On Error Resume Next nLevel = dPriorities.Item(sLevel) If Err.Number = 5 Then ConsoleWrite "Invalid selection of runlevel." & vbNewLine Syntax End End If On Error GoTo 0 If nLevel = 0 Then nInstances = KillProcess(sProcess) If nInstances = 0 Then ConsoleWrite "No instances of " & sProcess & " found to kill" & vbNewLine Else ConsoleWrite nInstances & " " & IIf(nInstances > 1, "instances", "instance") & " of " & sProcess & " killed." & vbNewLine End If Else ConsoleWrite sProcess & IIf(SetPriority(sProcess, nLevel), _ " boosted", " NOT boosted") & _ " to priority " & sLevel & " (" & nLevel & ")." & vbNewLine End If End Sub

What's next with this thing? I suppose one could explore the possibility of influencing the lives of applications on other computers:

BOOST Skype.exe kill /C:GUEST_01

There's also the fact that the commandline parser doesn't properly handle double-quoted names. If an .exe had a space it its name, you wouldn't be able use BOOST on it.

Finally, here's a short batch file (killall.bat) I use for killing applications en masse. It was originally designed to get around the 'typing the /P and /L' issue, but I'm so used to using it now ...

@echo off :loop if %1@==@ goto done c:\bin\boost %1 kill shift goto loop :done

An example invocation:

killall excel.exe outlook.exe

© Copyright Bruce M. Axtens, 2007

[VBScript] When did I log on/off?

The Australian federal government has brought in new laws which seem to require a return to the old days of clocking in at the beginning of the working day and clocking out at the end. As a contractor I don't think I'm going to notice a big difference ... if I want to get paid for the hours I work, then I fill out my timesheet appropriately.

If you aren't in the habit of keeping this kind of information, don't worry too much: Windows keeps a track of your login and logout in one of its Event Logs. Getting that information is fairly easy, if you know what you're looking for. Otherwise its like the proverbial needle in the haystack.

The script outputs into an Excel spreadsheet, the date of each logon in a separate column containing time of logon and logoff. Please note that the script was designed to query someone else's machine, and will likely need modification if you are trying to get your own data out of your own event log.

Here's the code.

As is often the case in my scripts, the preamble loads external code libraries. The former is a the standard library and the latter (see the end of the posting) a symbol table class, based on the Scripting.Dictionary object.

option explicit

Function GetEnv( strEnvVar )
    Dim oProcessEnvironment
    Dim sResult
    With CreateObject( "WScript.Shell" )
        GetEnv = .Environment( "PROCESS" )( UCase( strEnvVar ) )
    End With
End Function

Sub Include( scriptName )
    Dim sScript
    Dim oStream
    'on error resume next
    err.clear
    With CreateObject( "Scripting.FileSystemobject" )
        Set oStream = .OpenTextFile( scriptName )
    End With
    If Err.Number > 0 Then
        MsgBox "Could not open " & scriptName
        WScript.Quit
    End If
    Err.Clear
    sScript = oStream.ReadAll()
    oStream.Close
    ExecuteGlobal sScript
    If Err.Number <> 0 Then
        Die "Error in loaded script"
    End If
    On Error Goto 0
End Sub

Include "C:\Script\StandardLibrary.vbs"
Include "C:\Script\ClassSymTab.vbs"

Dim V
Set V = New Symtab

Next comes code to split up the event log's timestamp, followed by the routine to store logon date and logon and logoff times into spreadsheet cells.

function timesplit( sDateTime )
    timesplit = Left( sDateTime, 4 ) & "-" & Mid( sDateTime, 5, 2) & _
        "-" & Mid( sDateTime, 7, 2 ) & " " & Mid( sDateTime, 9, 2 ) & _
        ":" & Mid( sDateTime, 11, 2 ) & ":" & Mid( sDateTime, 13, 2 )
end function

Dim nECol
nEcol = 2

sub Excellent( dOn, dOff )
    oSheet.Cells( 1, nECol ).Value = DateValue( dOn )
    oSheet.Cells( 1, nECol ).Font.Bold = True
    oSheet.Cells( 2, nECol ).Value = TimeValue( dOn )
    oSheet.Cells( 3, nECol ).Value = TimeValue( dOff )
    oSheet.Columns(nECol).EntireColumn.AutoFit
    nECol = nECol + 1
end sub

Next comes the variable declarations. In retrospect the variables sComputer and sUser could have been Const rather than Dim. For that matter they could have been taken from the command line. Note the double backslash in the uUser variable: this is needed for where it occurs in the WMI call.

Const MAX_INSTANCE = 365

dim sComputer
Dim sUser
Dim oWMIService
dim cEvents
dim oEvent
Dim dLastDate
Dim aResults
Dim aRes
Dim n
Dim dLogin, dLogout
Dim aDates
Dim bFirst
Dim nInstance

sComputer = "THEMACHINE"
sUser = "THEDOMAIN\\theuser"

This is the core of the script: pointing WMI at sComputer and executing an SQL query against Win32_NTLogEvent. It asks for everything from the 'Security' Logfile where the EventCode matches a logon or a logoff and where the User matches sUser.

Set oWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _
        sComputer & "\root\cimv2")
Set cEvents = oWMIService.ExecQuery _
    ("Select * from Win32_NTLogEvent " _
        & "Where Logfile = 'Security' And _
        (EventCode=528 Or EventCode=538) And _
        User='" & sUser & "'")

Then the script starts to do things with the list of events now stored in cEvents. First a Dictionary is loaded with logons as (zero, comma, TimeSplit of datestamp) and logoffs as (one, comma, TimeSplit of datestamp). The reason for this is that there may be more than one logon and logoff event for a given user during a working day. By storing the logon and logoff times in this way, the first "0" reference can be assumed to be the first logon off the day, and the last "1" can be assumed to be the last logoff of the day.

dLastDate = dbDate( Cdate( 0 ) )

For Each oEvent in cEvents
    V.Store IIF( oEvent.EventCode = 528, 0, 1 ) & "," & TimeSplit( oEvent.TimeWritten ), vbNullString
Next

From the Dictionary wrapper class the keys are extracted. A check is put in here to make sure that there are records to be reported.

aResults = V.Keys()
'MsgBox Join( aResults, vbNewLine )
If UBound( aResults ) < 0 Then
    MsgBox "No records found"
    WScript.Quit
End If

Next comes the Excel interactions. The ExcelStart and ExcelNewSheet macros are listed at the bottom of this posting.

Dim oRange
Dim oSelection

ExcelStart False
ExcelNewSheet

oSheet.Cells( 2, 1 ).Value = "Logon"
oSheet.Cells( 3, 1 ).Value = "Logoff"
Set oRange = oSheet.Range( "A2", "A3" )
oRange.Font.Bold = True

What follows is the guts of the Excel reporting. Despite the possibility of incorrect recording, the assumption is that the report will contain the first logon and the last logoff. If a logon occurs after the last logoff, it is discarded. The script is unable to cope with the situation where someone logs on today and logs off tomorrow.

Note that a check is made not to report more dates than MAX_INSTANCE, a limit that has not yet been encountered. AMax and AMin are listed at the bottom of the posting.

aRes = Split( aResults( 0 ), "," )
dLastDate = DateValue( aRes( 1 ) )
ReDim aDates( -1 )
n = 1
bFirst = True
nInstance = 0
Do While True
    aRes = Split( aResults( n ), "," )
    If DateValue( aRes( 1 ) ) <> dLastDate And bFirst = False Then
        dLogin = AMin( aDates )
        dLogout = AMax( aDates )
        Excellent dLogin, dLogout
        nInstance = nInstance + 1
        If nInstance >= MAX_INSTANCE Then
            Exit Do
        End If
        ReDim aDates( -1 )
        dLastDate = DateValue( aRes( 1 ) )
    Else
        bFirst = False
        AAdd aDates, aRes( 1 )
        n = n + 1
        IF n > UBound( aResults ) Then
            Exit Do
        End If
    End If
Loop

Set oWMIService = Nothing
Set cEvents = Nothing

Excel is left running with the results of the report. It's up to the user to save it, print it or whatever. To finish, the macros ExcelStart, ExcelNewSheet, AMax and AMin, and the ClassSymTab class as promised.

Dim oExcel

Sub ExcelStart( bHidden )
    Set oExcel = CreateObject("Excel.Application")
    If bHidden = True Then
        oExcel.Visible = False
        oExcel.Interactive = False
    Else
        oExcel.Visible = True
        oExcel.Interactive = True
    End If
End Sub

Dim oWorkbook
Dim oSheet

Sub ExcelNewSheet()
    Set oWorkbook = oExcel.Workbooks.Add()
    Set oSheet = oWorkbook.ActiveSheet
End Sub

Function AMax( aVec )
    Dim vTemp
    Dim vResult

    vResult = aVec( 0 )

    For Each vTemp in aVec
        If vTemp > vResult Then
            vResult = vTemp
        End If
    Next
    AMax = vResult
End Function

Function AMin ( aVec )
    Dim vTemp
    Dim vResult

    vResult = aVec( 0 )

    For Each vTemp in aVec
        If vTemp < vResult Then
            vResult = vTemp
        End If
    Next
    AMin = vResult
End Function

Class symtab
    private oHash
    private sSystemPrefix

    Private Sub Class_Initialize()
        Set oHash = CreateObject( "Scripting.Dictionary" )
        sSystemPrefix = "$"
    End Sub

    Private Sub Class_Terminate()
        Set oHash = Nothing
    End Sub

    Public Sub Store( sName, vValue )
        If oHash.Exists( sName ) Then
            oHash( sName ) = vValue
        Else
            oHash.Add sName, vValue
        End If
    End Sub

    Public Function Recall( sName )
        If oHash.Exists( sName ) Then
            Recall = oHash( sName )
        Else
            Recall = Null
        End If
    End Function

    Public Function Keys()
        Keys = oHash.Keys
    End Function
    
    Public Function SymList()
        Dim nCount
        Dim aResult
        Dim aKeys
        Dim aItems
        Dim i

        nCount = oHash.Count
        'WScript.Echo nCount
        ReDim aResult( nCount - 1 )
        aKeys = oHash.Keys
        aItems = oHash.Items

        For i = 0 To nCount - 1
            'aResult( 0, i ) = aKeys( i )
            'aResult( 1, i ) = aItems( i )
            aResult( i ) = aKeys( i ) & "^" & aItems( i )
        Next
        'WScript.Echo UBound( aResult )
        SymList = aResult
    End Function

    Public Function SymListText()
        Dim aList
        Dim sItem
        Dim i
        Dim sResult
        aList = SymList()
        For i = 0 To UBound( aList )
            sItem = Replace( aList( i ), "^", "=" )
            sResult = sResult & sItem & vbNewLine
        Next
        SymListText = sResult
    End Function

    Public Function IsSym( sName )
        IsSym = oHash.Exists( sName )
    End Function

    Public Sub StoreDup( sName, xValue )
        Dim i
        Dim sNewName
        sNewName = sName
        i = 1
        If IsSym( sNewName ) Then
            Do
                sNewName = sName & "$" & i
                If oHash.Exists( sNewName ) = False Then
                    Exit Do
                End If
                i = i + 1
            Loop
        End If

        'WScript.Echo "StoreDup", sNewName, xValue
        Store sNewName, xValue
    End Sub

    Public Sub Parse( sData, sSep )
        Dim aData
        Dim i
        Dim sLine
        Dim aLine
        Dim sKey
        Dim sValue

        aData = Split( sData, vbNewLine )
        For i  = 0 To UBound( aData )
            sLine = aData( i )
            IF sLine <> vbNullString Then
                aLine = Split( sLine, sSep )
                sKey = aLine( 0 )
                sValue = aLine( 1 )
                sKey = UCase( RTrim( RemoveSpaces( sKey ) ) )
                sValue = RTrim( sValue )
                Store sKey, sValue
            End If
        Next
    End Sub

    Public Sub Remove( sData )
        IF oHash.Exists( sData ) Then
            oHash.Remove sData
        End If
    End Sub

    Public Sub Clear()
        Dim aList
        Dim i
        Dim sLine
        Dim aLine
        aList = SymList()
        For i = 0 To UBound( aList )
            sLine = aList( i )
            aLine = Split( sLine, "^" )
            If BeginsWith( aLine( 0 ), sSystemPrefix, False ) = False Then
                Remove aLine( 0 )
            End If
        Next
    End Sub
End Class

[VBScript and Excel] Relative/Absolute references

Again at Automate Excel In Vbscript... ( Vbscript ), Pentium10 wrote

I have a script which fills cells with exce.range.value function, but I have columns more than A-Z, how can I handle AA,AB, AC... columns???

Here is the script what I have:
excel.Range(chr(65+i) + str(excelrow), chr(65+i) + _
 str(excelrow)).value = lstOrder.cell(i,1)

And I wrote:

Re: I have a script which fills cells with ...

Function RelativeToAbsolute( aRow, aCol ) Dim alpha alpha = Split( "A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z", "," ) RelativeToAbsolute = alpha( aCol - 1 ) & aRow End Function That does me, but for you I'd suggest adding a few more items to the Split(). After Z put in ",AA,AB,AC," etc until you have what you need. Then code your references in terms of numeric column and a row and let the function generate a meaningful address.

For example: strRange = RelativeToAbsolute( 1, 1 ) & ":" & RelativeToAbsolute( 1 + iCount - 1, 1 ) oSheet.Range( strRange ).NumberFormat = "d/m/yyyy h:mm:ss" (iCount in this case is the number of rows in an array I was committing to the spreadsheet.)

[VBScript and Excel] Moving a sheet to the end of the list

Here's how to put the first sheet in a new spreadsheet at the end. This is a copy of a recent submission of mine at Automate Excel In Vbscript... ( Vbscript ) Set oExcel = CreateObject("Excel.Application") Set oWorkBook = oExcel.Workbooks.Add oWorkbook.Sheets("Sheet1").Move ,oWorkbook.Sheets( oWorkbook.Sheets.Count ) Note the comma after the space that is after the .Move. I'm specfying the "after" clause rather than the "before" and saying to move the sheet to after the last.

BTW, one of the best ways of finding out syntax is to record a macro and adapt the resulting code.