macro preventing document to be opened

[Guest]

Hopefully I can make some sense here.

Have an end user who is connecting to our Payroll terminal server via a
Winterm. Term serv is running W2k w/ Office 2002.

The document in question is housed on our file server, mapped to the 'N'
drive. I'm not sure what version of office the doc was created under.

EU was sent an email w/ the doc attached. When she tries to open or save the
doc, (named: "Payroll Adjustment Notification Termination Form"), she gets
the following error: "Can't create file: 'Payroll.....'. Right click the
folder you want to create the file in, and then click Properties on the
shortcut menu to check your permissions for the folder" This happens when
she tries to attach the document to an email as well.

If we rename the file, she can open it, save it, attach it etc... If someone
sends her the file renamed, she can open it etc... But again, if the
title/name of the doc is not changed and sent to her, she gets the error
message.

I've checked her permissions, checked the permissions on the doc etc... and
all check out as they should. I've copied the doc over to her user folder
(where she'd be the owner), but we still get the error.

Other users can open the doc no problem, and this is the only doc that she
is having troubles with.

We seem to have narrowed it down to a macro that is running on the doc. The
macro seems to be checking against the name of the doc and preventing her
from opening it up. Macros is/are set on "high" and the doc is protected,
but only to preserve formatting.

Is there any way to figure out where w/in the macro it's set to cause this
and edit?

Thanks in advance,

Jim

 

[Charles Kenyon]

This does _not_ sound like it is a macro. I suspect that your user has
either an earlier version of the file, write protected, in that folder or a
lock file from the file. It would be named something like ~ayroll Adjustment
Notification Termination Form.doc and may be hidden.
--
Charles Kenyon

Word New User FAQ & Web Directory: http://addbalance.com/word

Intermediate User's Guide to Microsoft Word (supplemented version of
Microsoft's Legal Users' Guide) http://addbalance.com/usersguide

See also the MVP FAQ: http://www.mvps.org/word which is awesome!
--------- --------- --------- --------- --------- ---------
This message is posted to a newsgroup. Please post replies
and questions to the newsgroup so that others can learn
from my ignorance and your wisdom.

 

[Guest]

It may not be a macro, but it's not quite what you refer to either.

The doc isn't hidden, it's not write protected and it's not an older version.

Other users can open this doc (I can open the doc).

No attributes on the doc have been changed. We can simply add an underscore
to the end of the docs name, and then she is able to access it in every way
that she can't when the doc is in it's original name format.

-jim

 

[Charles Kenyon]

The lock file I am referring to would be a hidden file. It would be in the
user's folder. It would prevent anyone from saving a file with the name you
describe from saving under that name because the computer would believe the
file already exists. Do you understand Word's user locking files?
--
Charles Kenyon

Word New User FAQ & Web Directory: http://addbalance.com/word

Intermediate User's Guide to Microsoft Word (supplemented version of
Microsoft's Legal Users' Guide) http://addbalance.com/usersguide

See also the MVP FAQ: http://www.mvps.org/word which is awesome!
--------- --------- --------- --------- --------- ---------
This message is posted to a newsgroup. Please post replies
and questions to the newsgroup so that others can learn
from my ignorance and your wisdom.

 

[Guest]

Hmmm...apparently not. What would be the name of the lock/hidden file, and
which folder would it reside in?

Better yet, can you point me in a direction I need to go?

thanks,

Jim

 

[Suzanne S. Barnhill]

If your file is named Filename.doc, the "lock" file will be ~$lename.doc.

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA

Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.