DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=DD
	Q7Pf88GC5YwGSRqhu04/KZDuTp+Ddsi3aMIolBYy6MBOsYmlEBsZIkHaP2vrcRE9
	no17VmNprKnMZrB30IfCV/vvm45kKZPdAU+zWTeqfaWN90hMdX5G4P9xgaPdNEPL
	KsiAY2yTSxBX/n+ppHUI9ZjT2gxiCH9pFhMTNLNhM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <883F2CBBC85A62419E181EB2F0ECF21F45DE3251@US70UWXCHMBA04.zam.alcatel-lucent.com>
References: <883F2CBBC85A62419E181EB2F0ECF21F45DE3251@US70UWXCHMBA04.zam.alcatel-lucent.com>
Date: Tue, 16 Jun 2015 21:21:24 -0400
Message-ID: <CADi7v6K2NiQGVEgPRFr_yFp_eJ1VrZ32gWp7CNhFixGpB3NiYg@mail.gmail.com>
Subject: Re: Unable to run excel via cron
From: Bryan Berns <bryan.berns@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

On Tue, Jun 16, 2015 at 9:27 AM, Kertz, Denis (D)** CTR **
<d.kertz@alcatel-lucent.com> wrote:
> We need to run some Excel programs via cron and are using vbscript to do this.  We have this running on a WinXP machine but are having trouble running on a Win7 machine, but we don't think it is a Win7 problem.
>
> Here's the script to run a simple test excel program:
>
> Dim xlApp
> Dim xlWb
> Set xlApp = CreateObject("Excel.application")
> xlApp.Visible = True
> Set xlWb = xlApp.workbooks.Open("c:\Shared\Prospect\Bin\TestExcel.xls")
> xlApp.Quit
> Set xlWb = Nothing
> Set xlApp = Nothing
>

What bitness of Excel and Cygwin are you running?

CreateObject("Excel.application") will attempt to create a 32-bit
instance of Excel when launched through the 32-bit version of
wscript.exe or a 64-bit instance of Excel when launched through the
64-bit version of Excel.  Which bitness of WScript.exe ends up being
run will depend on the bitness of the parent program (which may be
different in a command prompt vice Cygwin).  Try changing it to run
Wscript.exe in SysWow64 instead of System32 (which is subject to
automatic redirection) and see if changes the behavior.  If you're not
running a 64-bit OS, then just ignore everything I said.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple