Chip,
I looked up a note I had made and am wondering if this has something to
do with your problem.
I don't know as much about programming as I will some day, but would it
be better to use "GetObject" rather than "CreateObject"?
Here's the note I had made some time ago:
'To instantiate the window-eyes object externally,
'use either of these forms:
'set WO = GetObject("","windoweyes.application")
'or
'set WO = createObject("windoweyes.application")
hth,
Rod
Subject: low-level type of question
From: "Chip Orange"
<[email protected]>
Date: Sat, 7 Sep 2013 17:40:59 -0400
Reply-To:
[email protected]
Hi all,
For those of you who understand the really low-level way in which things
work, I wonder if you could guess at a problem I'm having (I'm just curious
as to why, not that I expect anyone to solve it).
At work I sometimes program in visual foxpro; an interpreted macro language,
much like VBScript. I frequently use activeX objects in these programs.
Recently, because I've learned about the scripting object
scripting.dictionary from my work with Window-eyes, I tried to use this
object in VFP programs. While it executes the CreateObject() just fine,
whenever I try to use any of the methods or properties of the
scripting.dictionary object I get an error from VFP that the property or
method can't be found.
Just wondering if there are different low-level standards for interfacing
with COM objects, and does the scripting.dictionary object require a
specific one (which VFP might not support)?
Thanks for any clues here.
Chip
