Recent content by Simon Goodman

Will review on Wednesday, thanks.

I have tried this, and wsh.Run does not start WB2 at all. If I use a straight Shell command, it works but asynchronously. If I place a MsgBox after the Shell command, the process is effectively correct. What might be going wrong?

Again, thanks. I'll see if this sorts my process out.

Can I ask? What is the reason for using CreateObject, rather than simply running the Shell command directly? What is the wsh.Run command? What is the expected value of exitCode? Thank you very much for your assistance.

Thank you! I'll try that tomorrow, when I'm back at work.

I am developing a macro, contained within an Excel workbook (call it WB1). Via an auto-open process, it starts another Excel workbook (WB2). The auto-open process of WB2 then runs. At the end, it writes a value to the Registry. When completed, control returns to WB1. This reads the Registry...

I thought Command() was an Excel command? I certainly haven't defined it. If this is the case, I need a simple way of passing a string value from one workbook to another, where the 2nd workbook is running as a separate invocation of Excel.

Thank you for your helpful suggestions, Lutfor. I'm not in work until Wednesday, so will try when I'm there. I'm in PDT time zone.

I don't think I explained this situation clearly enough. The command function is in the auto-open macro, as contained in ThisWorkbook section of the VBAProject for Excel workbook I am opening. I have tried opening this workbook using a Powershell script, another workbook using the Shell...

I am trying to pass a parameter to an Excel VBA macro, to be accessed by the first statement in the auto-open macro of the workbook. Whatever happens I always get a null result from the function Command(). No error is recorded. How can I correct this or investigate further?