DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=n+t
	iwiOYq42NAuMf/w34nBDUzkeGl0pJ7JcqsUjFX/7nr2IrUby4C8dlghSg/bY0IIA
	ueRqElAiCCPHhQkSDlECVtlueUu23yvTB9Tq8etfqVE4XxklCUCB7oza8TzTuEf/
	yiBNswXxKxvLRQOR1PWUE1bnN+mnXxh7uWoBKatI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Kertz, Denis (D)** CTR **" <d.kertz@alcatel-lucent.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Unable to run excel via cron
Date: Wed, 17 Jun 2015 13:29:00 +0000
Message-ID: <883F2CBBC85A62419E181EB2F0ECF21F45DE3905@US70UWXCHMBA04.zam.alcatel-lucent.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Unfortunately, using the 64-bit wscript.exe didn't change anything - same behavior as before with excel hanging.

We are using 64-bit cygwin and 32-bit Excel (Excel 2007).

Denis

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