23-Mar-2006

Remote-Save & Volume rename problem.

Specs: Win XP Pro SP2, Word 2003 [working on small Home Net LAN]
--------------------------------

Below is a macro which, when run, saves a Word doc to:

(1) CURRENT comp (COMP-1, local) and folder, then to a
(2) BACKUP location (over LAN, to COMP #2) and, finally, again locally, to
(3) CURRENT COMP & folder - in order to put focus back on current folder.

I got the basic macro from a site to which I was referred to from one of
the Microsoft forums (in 'Win XP Gen', I think).

It works just fine:

--------------
Sub WORDBAK2()
'
' SaveDocToTwoLocations
' WORDBAK2 Macro
' Macro created 21/02/06 by PC
'

Dim strFileA, strFileB, strFileC
ActiveDocument.Save
strFileA = ActiveDocument.Name
'Define backup path shown below
strFileB = "\\COMP-1\D\COMP-2_WordBaks\Backup " & strFileA
strFileC = ActiveDocument.FullName
ActiveDocument.SaveAs FileName:=strFileB
ActiveDocument.SaveAs FileName:=strFileC
End Sub
--------------

Yesterday, while checking the document BACKUP target location at COMP-2, I
think I saw a blank in the Volume name entry for logical drive D: while
checking Properties to make sure "Share" was on for D:, and may have typed
in "BACKUP" or similar, for the Volume Name first. Fact is, I'm not really
sure if supposed to type anything at all into that box - but the cursor
was blinking in it and it was right next to the drive icon.

From then on, the macro at COMP-1 kept coming up w/ error message about:
"this is not a valid path" and so on, and stops at:

"ActiveDocument.SaveAs FileName:=strFileB".

I should point out also that, at COMP-2, *BOTH* the target drive (D AND
the target FOLDER in it had to be fully "shared" in order for the BACKUP
save to occur over the LAN, from COMP-1 to COMP-2. That's a fact. If only
one or the other was a share, the backup save wouldn't work ("invalid
path...", etc.). This would appear not to be the best way to go because even
Windows warns about potential risks of "sharing" whole drives. So why then
is this necessary when only a 'folder' in that drive is the target?

Tried renaming volume back & forth (which was not easy) but nothing helped.
Finally had to change BACKUP location to drive C: and adjust macro target
path accordingly. That works OK but space on C: is limited and "share" has
to be enabled - not a wise thing to do for the root drive, I understand.

Before anyone suggests the obvious, no, the backups couldn't be made to
another "folder" on drive "D:" of COMP-2. Tried that. Same problem. So
must be something to do with the Volume name for drive "D:".

At moment, in Explorer view, the drive D: volume name (or label, or
whatever) is shown as: " BACKS(D (D ". I don't quite know how I managed
to do that. However, now I'm unable to RENAME to just the usual "(D", no
matter what I do. I un-shared D: and the 4 sub-folders under it (which were
also share-enabled) before trying to rename the drive back to normal - but
this was no help.

When structure is viewed via dble-click on "My Computer", both volumes are
displayed simply as: "Local drive (C" & "Local drive (D". In properties
for each drive, the box for drive or volume name on "General" tab is empty.

COMP #1 happens to have an SCSI drive, which is partitioned into a FAT32
(C:, Primary drive, w/ XP running on it) and an NTFS (D drive - mainly
for Backups.

When I right-click on "My Computer" and then click Properties, Advanced,
Hardware, Device Manager, Disk Drives, ST380311, then right-click for
Properties, and then 'Volumes' - there are no entries whatever under
"The Volumes contained on this disk are listed below:".

That is, there are about 8 items listed - but the blanks for data next to
each entry are empty (ex: Disk: ____ ; Type: ____ ; Status: ____ ; etc.).

To reiterate, ALL was working fine w/ the macro since late February, until
I went to double-check the Properties for drive D:, just a day ago.

Now it remains for me to find an easy way to get that Vol name back from
the weird "BACKS(D (D" to just "(D", as I believe it was originally.

I wonder if these difficulties arose partly due to the fact that COMP # 1
has an SCSI drive and COMP #2, an IDE drive, with both having a prime FAT32
partition and a 2nd, NTFS partition. It is of course the NTFS partition
at which we're having the Volume/Label rename problem.

Can anyone shed any light on this situation?

As usual, greatly appreciate any help.

--
Ted...