MSched v9 trying to open the clipboard

[Captive]

(Even though I mention nntp and clipmagic - this issue is msched related. Marcus if you want to / want me to remove the reference to the non-mjt software here I fully understand.)

I've recently started experiencing a minor issue regarding clipboards. A certain nntp program I use will decode certain posts via the clipboard before displaying them. I discovered this because if I have clipmagic enabled and I skip through posts too quickly it (clipmagic) gives me an error.

After I upgraded to Macro v9, and using this nntp program, I will regularly hear a beep/ding, and msched presents a small dialog with "Cannot open clipboard." - I can click OK and all seems to be ok.

The odd thing is - I'm not running any msched scripts. It shouldn't be trying to open my clipboard in the first place. Also, the other apps I use that can potentially monitor/open should not be doing so at the time.

The error only seems to occur when I go through nntp posts very quickly - ie, hitting next 2+ times each second.

MSched v9.0.53
OS: WinXP Pro

Also running:
ClipMagic v3.2.3 (Capture = off)
Clipomatic v2.01 (Clipboard caching disabled)

[IowaTool_Jim]

I am seeing this too when I use the Run Program command to start Excel, e.g.:

Run Program>C:\Program Files\Microsoft Office\Office12\EXCEL.EXE

Excel starts fine, but back in the MSched editor I have two or three mini-dialogs saying "Cannot open clipboard."

I assume there is a better/different way to launch an Office program using VBA, but I don't know it offhand and figured that I'd just use the obvious solution available. (I don't know how to, or if, namespaces such as Microsoft.VisualBasic can be referenced within a MSched VBScript block within a macro.)

ALSO, and this seems strange... If I have the MSched editor open when I launch Excel 2007, I get those same two dialogs. IOW, I don't have to execute a macro to get MSched to pop these dialogs, they happen even when I simply launch Excel directly. (This does not happen for other MSOffice apps.)

I'd be happy to detail any additional info needed to figure this out.

--Jim--

[Marcus Tettmar]

Unable to replicate. Anyone else seeing this and got steps to replicate?

[IowaTool_Jim]

I determined that my "Cannot open clipboard" dialogs were happening when I did either an MacroSched 'Run' command or a VBScript 'CreateObject' command to open an Excel instance when one was already running.

What works for me is to open Excel in a VBScript block using GetObject rather than CreateObject:

Set oExcel = GetObject( , "Excel.Application")

Note the empty first parameter (the 'space comma space' bit) rather than CreateObject's single 'Excel.Application' parameter. The GetObject approach works whether an instance is open or not, so there is not -- for my application at least -- any downside to this. The benefit is no more little 'Cannot open clipboard' dialogs.

--IowaTool_Jim--