|
Paul, Sometimes
Wait is used before the first Connect, in which case it may not have created
Boston WorkStation’s WinScript object to make Wait’s
code available. Could this be
possible? -----Original Message----- I’ve been attempting
to run a Windows script, and am getting an Automation Error when it attempts to
do a “Wait” It doesn’t happen
every time, so I’m not sure why it’s happening. Any Ideas? Paul -----Original
Message----- I
thought we might avoid all the email security hassles, but no such luck… We’ve
received a Security Bulletin from Microsoft about a security patch for VBA associated
with loading VBA project. Since we
share VBA with other Microsoft applications (Office, for example), it’s
likely that a breach would occur from loading a Word document containing VBA
code rather that loading a *.bws file.
However, the possibility exists.
The Security Bulletin can be found at: http://www.microsoft.com/technet/security/bulletin/MS03-037.asp and the
patch can be found at: http://www.microsoft.com/downloads/details.aspx?FamilyId=DA1A7ABA-CD3D-458B-9729-AB9094C9BD3F We’ve
been running with the patch for a few days without observing any effects. Shortly, we’ll send this message
to our current customers and we’ll be incorporating the patch into the
base product. Feel free to contact
me if you have any questions. Rich McNeil 866 653 5105 |
- [Talk] Boston WorkStation Security Patch to VBA Rich McNeil
- RE: [Talk] Boston WorkStation Security Patch to VBA Paul
- Rich McNeil
