Install Problem with OLE Automation

[jpugh]

I have an app that uses OLE to place data into a Word document. On my development system, it works just fine, but on my customer's system, nothing happens - no error messages; simply no response.

I suspect that something is missing from by install setup (I'm using VFP 7.0, so it's InstallShield), but I have no idea what it might be.

Any ideas would be much appreciated.

Thanks,
Jon

 

[rgbean]

Jon,
I hate to ask the obvious, but since you didn't say - Does your user have the same version of Word / Office installed as you do? Also, are you using the same OS and "update" level (SP, HotFixes, Security Patches, etc.)?

Rick

 

[jpugh]

Rick,

Good question. Our OS (WIN2000) is the same, however our versions of MS Word are different.

I'm not sure why this would make a difference, since I didn't think the VFP app would carry any info about the version of Word it was instantiating. What am I missing?

Jon

 

[jhall156]

The exposed automation objects are different for different versions of word. Are you using the ProgID to create the automation object?

 

[jpugh]

It turns out that Rick's first inclination was on target - it was something really obvious. The fact was that the code that creates the Word.Application object was not even running on the client system. I was checking for a .DOC file that was in the wrong place and when it wasn't found, the code was bypassed.

Now that it's working I can safely say that it shouldn't matter what version of Word (within reason) is on the target machine, opening it as an OLE object should work.

Thanks for both your replies.
Jon

 

[rgbean]

Jon,
I'm glad it was so &quot;obvious&quot;. Sometimes just having someone suggest you look at the code with fresh eyes, can fix these little &quot;problems&quot;. <g>

Rick