Word MS Access Wordpad OLE objects

[ajetrumpet]

Hello everyone,

I have a general question about Wordpad OLE objects. I have the following code snippet:

		 Forms![FormLetters]!MyOle.Verb = -2
 		Forms![FormLetters]!MyOle.Action = 7
 		 Set Word_Obj = Forms![FormLetters]!MyOle.Object.Application.WordBasic
 
 Word_Obj.FileSaveAs ("c:\Letters\mydocument.rtf")

It opens up the OLE document and saves it to a directory. This will not work with a wordpad document however. I get the error "automation object does not comply with the file", or something to that effect. Makes perfect sense. But, how do I open up WORDPAD instead of the WordBasic object so I can use that program instead to save the file? I tried this:

Set Word_Obj = Forms![FormLetters]!MyOle.Object.Application.WordPad

but it did not work so well.

Thank you for any help!

 

[JaLing]

We generally use Wordbasic for anything like this m8.

The main reason is as follows

Microsoft Security Bulletin MS07-011
Vulnerability in Microsoft OLE Dialog Could Allow Remote Code Execution (926436)
http://www.microsoft.com/technet/security/bulletin/ms07-011.mspx

It's possible that the fix prevents what your trying to do but without the entire code I can't tell you if that's the case.
(You have added the OLE object via the References bit in the IDE haven't you ?)

 

[ajetrumpet]

We generally use Wordbasic for anything like this m8.

The main reason is as follows

Microsoft Security Bulletin MS07-011
Vulnerability in Microsoft OLE Dialog Could Allow Remote Code Execution (926436)
http://www.microsoft.com/technet/security/bulletin/ms07-011.mspx

It's possible that the fix prevents what your trying to do but without the entire code I can't tell you if that's the case.
(You have added the OLE object via the References bit in the IDE haven't you ?)

Well...for one thing, the article says that Vista is not affected. That is my OS. Are you saying that the WORDPAD syntax that I used before SHOULD work? If not, any other ideas?

 

[JaLing]

Check
http://msdn.microsoft.com/en-us/library/51y8h3tk(VS.80).aspx

It's all I could find about it.... however I never used it due to best practices.
It's a OLE2 object btw so that could be part of the issue for you.

BTW when MS say a newer OS isn't affected by something thats because the fix is already built into it.