Word 2000 macros can no longer create text file

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Greg Smith - 16 Jun 2005 21:47 GMT

We have been running document processing macros for many years. As part of
this, they do:

Open filename$ for Output as #1
print #1, contents$
Close #1

Recently (in the past few days) this has stopped working. The symptops are
consistent with VBA refusing to create or write to external files. If I
change Output to Input then read, this works, so it is not a problem with the
path. We suspect that a recent security patch from Microsoft is responsible.
We have seen this on two computers, both running XP SP2 and both with all the
latest security patches.

Help!

Reply to this Message

Word Heretic - 16 Jun 2005 23:13 GMT

G'day "Greg Smith" <Greg Smith@discussions.microsoft.com>,

I just ran a test on my up-to-date Win XP, Word 2k machine and it
worked fine.

Steve Hudson - Word Heretic

steve from wordheretic.com (Email replies require payment)
Without prejudice

"Greg Smith" <Greg Smith@discussions.microsoft.com> reckoned:

>We have been running document processing macros for many years. As part of
>this, they do:
[quoted text clipped - 11 lines]
>
>Help!

Reply to this Message

Tony Strazzeri - 17 Jun 2005 04:46 GMT

Hi Greg,

given that you can read the file, then the path must be Ok. My
suspicions would be that the file or folder has been made read-only.

Cheers
TonyS.

> We have been running document processing macros for many years. As part of
> this, they do:
[quoted text clipped - 11 lines]
>
> Help!

Reply to this Message

Greg Smith - 17 Jun 2005 10:08 GMT

I thought about read-only too. If I display the file attributes, the file is
not read only. I also checked the folder read-only attributes. The read only
check box in folder properties is not clear... it has a grey tick. I have
tried clearing it, which perports to work, but when next you open the
properties box it is back as a grey tick.

I am logged on as a member of the administrative group. The folder was on a
local, shared volume, but the problem remains when I stop sharing it.

The security settings for the folder allow me full access.

--------------------- deep though ------------------------

OK ... I have figured it out. We recently installed the latest update to
Kaspersky anti-virus 5.0. If I disable this, the problem goes away. Sorry to
waste everyones time... I'll get on to them.

Thanks for the sensible suggestions.

Greg Smith

We have

> Hi Greg,
>
[quoted text clipped - 19 lines]
> >
> > Help!

Reply to this Message