I've been following this thread, but I don't remember -- has anyone suggested writing a regular Visual Basic program to automate Word? It's not too difficult to convert VBA code to VB. The VB runtime comes with newer versions of Windows. However, older versions would require the runtime to be installed along with the executable.
It should be possible to write it against an older version of Word and still be compatible with the newer versions. I don't think the macro setting would affect an external program, but I don't know for sure. Steve Trandahl -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nichols, Lester Sent: Tuesday, November 25, 2003 6:55 PM To: '[EMAIL PROTECTED]' Subject: RE: [sword-devel] Re: HELP WANTED -- OPPORTUNITY TO SERVE Just another note about using the macros and VBA. The latest versions of 97 with sp/2000 with sp/XP all have macros disabled by default. After looking at the instructions, there is no reference as to how the user would enable macros. The instructions list the way to select enable macros if prompted. The newer security patches and software does not even prompt you, but disables macros completely, where there are no prompts without manual intervention. Also the enabling of the macros will also pose a security risk and potential virus threat to those using the macro. This in turn could cause much more harm then good, especially if the end-user is not careful. I have attached the vba code for the various macros as a text file. I have tried it on a P4 XPsp1 system running Office XP SP2 and the macros do not run. The runtime errors that I get I think are do to the difference in vba global objects in the version I have. I have not tried them on another version of windows or office as of yet. The version of vba I am running is 6.4.8869. I did also note that office XP is not a part of the "versions" that could be used. Another item not listed is Microsoft works which uses word from xp. I can understand where the end-user would become frustrated with the various processes to complete and then troubleshoot. I still believe that the simplest path would be to use an alternative to MSO. Any thoughts? Lester Nichols "Embrace the Virtual Mindshare" Network Engineer Information Technology Services [EMAIL PROTECTED] www.lesternichols.com Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not directly or indirectly, use, disclose, distribute, print, or copy any part of this message to anyone. If you have received it in error please advise the sender immediately by return email and then delete it and all copies from your system. Community Bank reserves the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. No contracts may be concluded on behalf of the sender by means of electronic communications unless expressly stated to the contrary. _______________________________________________ sword-devel mailing list [EMAIL PROTECTED] http://www.crosswire.org/mailman/listinfo/sword-devel
