R
roundhouse
Here is my experience with this problem:
networkeer to peer xp,me,98 - most user documents stored on ME machine
First reported as "can't save as" in Publisher (office xp on xp-sp1 machine)
to networked folder - on ME machine. Soon complaint about Word and Excel
having same problem. User had admin rights on the xp system. Had been using
this configuration for about 1 year with no problem. I went to another xp
machine and logged on as the user and had no problem opening the file and
doing "save as". This machine had sp2 and probably had NOT had the updates
installed. Trying to pin down the problem I went back to the first machine
and tried saving some test files. Both notepad and wordpad allowed "save as"
on both the ME and the other XP machines. Could not "save as" in office XP
programs to the other XP machine (or the ME).
From this all I could conclude was that the problem was in the office
package and NOT network related.
This started about a month ago - user is getting tired of work arounds such
as save to local drive - move to networked floder, or copying and renaming
networked file first to allow editing and saving. This week the user of the
xp-sp2 machine reported same problem - I'll bet the updates have been applied!
Does anyone know how the updates relate to The Microsoft Office XP
FileDialog Object? Specifically the
"SaveAs Dialog (msoFileDialogSaveAs) - allows users to select a single file.
If you choose to do so, you can then save the current file by using the
Execute method"
see knowledgebase article ID 288543 for using this dialog
The fact that only Office "save as" seems to be having this problem makes me
think this might be a good place to at closely.
Thank you all for this thread - I was getting nowhere until I found this
site. It really makes one look bad when all you can say to the victim
is"damned if I know what's going on!"
networkeer to peer xp,me,98 - most user documents stored on ME machine
First reported as "can't save as" in Publisher (office xp on xp-sp1 machine)
to networked folder - on ME machine. Soon complaint about Word and Excel
having same problem. User had admin rights on the xp system. Had been using
this configuration for about 1 year with no problem. I went to another xp
machine and logged on as the user and had no problem opening the file and
doing "save as". This machine had sp2 and probably had NOT had the updates
installed. Trying to pin down the problem I went back to the first machine
and tried saving some test files. Both notepad and wordpad allowed "save as"
on both the ME and the other XP machines. Could not "save as" in office XP
programs to the other XP machine (or the ME).
From this all I could conclude was that the problem was in the office
package and NOT network related.
This started about a month ago - user is getting tired of work arounds such
as save to local drive - move to networked floder, or copying and renaming
networked file first to allow editing and saving. This week the user of the
xp-sp2 machine reported same problem - I'll bet the updates have been applied!
Does anyone know how the updates relate to The Microsoft Office XP
FileDialog Object? Specifically the
"SaveAs Dialog (msoFileDialogSaveAs) - allows users to select a single file.
If you choose to do so, you can then save the current file by using the
Execute method"
see knowledgebase article ID 288543 for using this dialog
The fact that only Office "save as" seems to be having this problem makes me
think this might be a good place to at closely.
Thank you all for this thread - I was getting nowhere until I found this
site. It really makes one look bad when all you can say to the victim
is"damned if I know what's going on!"