Results 1 to 8 of 8
  1. #1
    Star Lounger
    Join Date
    Jul 2001
    Location
    Edison, New Jersey, USA
    Posts
    89
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Macro path definition prob. (MSWord 2000/ WIN XP)

    I have a macro with the following line:
    strFilespec = "ServerS_DataDocumentsShared DocsPreQuals" & GetDocProperty("CCG_Filename") & ".doc"

    Its purpose is to define the folder location and filename.doc for saving the document created by a template.
    It used to work just fine. Now it resolves the filename ok, but it does not position at the specified folder (it uses whatever folder location was last used).

    If I change this line to:
    strFilespec = "DocumentsShared DocsPreQuals" & GetDocProperty("CCG_Filename") & ".doc"
    then it works fine, but I would have to modify the macros for every client that I install on.

    I have verified that the system name is "Server" and that the drive name is "S_Data". I have played with some capitalization modifications and the caps don't seem to make a difference. I have another program that links to shared folders on this shared drive using ServerS_Data and it links ok. Something about these macros is throwing this out of kilter...

    Any ideas?

    TIA

    p.s.
    I hear: If it used to work, What Changed?
    I am not 100% sure I know when this stopped working Correctly (e.g. user does not notice Where file is being saved - it saves, he/she keeps on keeping on...); but I had another Weird problem last week: I have a laptop that takes advantage of XP Pro's file synchronization feature. Every time the laptop is booted up or down, it re-syncs files on the server. This gives me a full set to work with at a home as well as a "back-up". The file sync decided it could no longer find the "path name". Took me days of playing around to get it back to working order. I ended up deleting all sync'd files off the laptop; turning off the Work offline feature; making all my shared drives on the Server, not shared; and then reversed the steps to re-establish the sharing of the drives, and file offline working and re-sync'd all over again. File Sync working as it should now. As I said, not sure if / how this is related, but it seems like the macros have a similar problem - can't "find the path name" . Anyway, the actual names of the PC and Drive match those in the macros. (This is a WINXP Peer-to-peer network, with some XP Pro and some XP Home. Running SP2 on all but one system that just goes crazy every time we try to load SP2... buts that another story).

  2. #2
    Plutonium Lounger
    Join Date
    Nov 2001
    Posts
    10,550
    Thanks
    0
    Thanked 7 Times in 7 Posts

    Re: Macro path definition prob. (MSWord 2000/ WIN XP)

    If you kinow the fully quallified domain name (FQDN) of server, then you could try using this instead of Server
    For example Server.mydomain.com or whatever

    StuartR

  3. #3
    Star Lounger
    Join Date
    Jul 2001
    Location
    Edison, New Jersey, USA
    Posts
    89
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Macro path definition prob. (MSWord 2000/ WIN XP)

    StuartR,
    My network is a Peer-to-Peer network so I don't have a Domain name such as in a true Client / Server environment. I just use the names Server and Client because of the logical fit. It is my understanding that my ServerS_Data... is a Fully Qualified Name for my environment (just not a Fully Qualified Domain Name). computer_namedrive_labelfolder_path is the format I am using.

    Technically I am using what's called Universal Naming Convention (UNC) names (not Fully Qualified Names).

  4. #4
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: Macro path definition prob. (MSWord 2000/ WIN

    I'm inclined to say "that's impossible" when UNC_Path_A gets changed to UNC_Path_B by Windows. Server names can be redirected (misdirected?) in a hosts file, but I'm not aware of any way that Windows could mistake one absolute path for another.

    As for using a drive mapping, you could try creating your own drive mapping. I think there is a way to do this using the Windows Script Host, or for sure there is a way using the Windows API. Then you could use a consistent letter in your code... assuming that letter is not already assigned to another network drive. <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

  5. #5
    Plutonium Lounger
    Join Date
    Nov 2001
    Posts
    10,550
    Thanks
    0
    Thanked 7 Times in 7 Posts

    Re: Macro path definition prob. (MSWord 2000/ WIN XP)

    Could you please double check this for me by typing the command IPCONFIG / ALL in a command window and looking for the value of "Connection-specific DNS suffix" on your network adapter. This is the bit that you would add after server.

    StuartR

  6. #6
    Star Lounger
    Join Date
    Jul 2001
    Location
    Edison, New Jersey, USA
    Posts
    89
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Macro path definition prob. (MSWord 2000/ WIN

    Stuart - that field ("Connection-specific DNS suffix") is blank. This is consistent with the entries at My Computer/Properties/Computer Name. The PC's in our small peer-to-peer network belong to the same WORKGROUP and no DOMAIN is defined.

    Jscher2000 - My last resort will be to Define the mountings for the shared drives on each PC to match the drive letter assignments on the Server PC. I actually did it this way some years back because I was running an application that "required" it be done that way for some reason. What a pain. Using the Universal Naming Convention (UNC) approach, after that software was updated, was a Delight and it worked fine until just recently.

    So I'm still scratching my head trying different things as I find the time (e.g., replacing the "space" in the folder name with an "underscore" did not help). I also changed the names (PC name and Shared Drive name) to something different and then changed them back - no help). Maybe I should try to back out some of the XP updates...

    Many thanks to you folks for giving my problem some thought.

  7. #7
    Star Lounger
    Join Date
    Jul 2001
    Location
    Edison, New Jersey, USA
    Posts
    89
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Macro path definition prob. (MSWord 2000/ WIN XP)

    Ok, Got it working. I have no idea which of these actions was the magical one, but in the end, my problem is solved. Here is my logic and what I did:

    Identified the critical components as Computer Name, WORKGROUP, Names of Shared Logical Drives, Sharing Properties of those drives. The plan: Undo everything, Redo everything.

    Booted to Safe Mode: Learned that none of the sharing attributes are even visible so this is not a good place to start. Why Safe Mode? Because much of what I intend to do, I already tried once and it didn't help. I suspect that something else in the network or on my box my have prevented something on some level. Reasonable paranoia for a guy who really doesn't understand what he is doing or the complexities of Windows, etc.

    Re-booted to Safe Mode with Networking. Changed Computer Name, WORKGROUP, and Logical Drive Names to something else, a name I do not intend to use/keep. The Sharing/Security surprized me. Showed names as D$ and F$ (the 2 logical drives are my D & F drives. A drop down showed the names that I knew and loved. I turned off file sharing. I verified that Simple File Sharing was still ON (box checked). I unchecked and re-checked, and said Reset all Folders and Apply to All folders. I made note of which fields are shown a certain way by WINXP (e.g., the Computer Name is always displayed with the first letter as upper case and the others as lower case, WORKGROUP always shows everything as uppercase)

    Re-boot to Safe Mode w/Networking again. Set the Computer Name and WORKGROUP to values I really want to keep. I used the "display preference" as my model (I used the shift key to get upper case when I knew that the display would show upper case anyway). Changed the Logical Drive names to those I wanted. Verified Simple File Sharing still on.

    Re-booted to Safe Mode w/Networking again. Set the sharing attributes I desired. This surprised me too. I went to Properties for each drive to get to the Sharing attributes. Had to create New Shares because the only names that showed were the funny D$ and F$ names. I gave each New Share the name I knew and loved (the Logical Drive names). Then went to Permissions. Set Everyone to Full Control (default was Read Only). Decided to leave Caching Settings at "Manual Caching" - seemed reasonable, but I'm working with nada for knowledge/experience. Then noticed that even though I created New Shares for my Logical Drives, WINXP insisted on reverting to D$ & F$ even after I selected my names from the dropdown that displayed my names. OK - I'll boot again and change it...

    Re-booted with a Full Boot. Verified that Computer Name and WORKGROUP were correct. Verified Simple File Sharing still on. Verified Sharing attributes - surprized me again... The names I created in the previous step were showing instead of the D$ and F$ that WINXP had insisted on. I didn't have to select them from the dropdown field. (Fuzzy memory here - I don't recall if the dropdown was even available to select D$ or F$ - didn't care enough to notice I suppose as my desired names were in use.

    Re-ran my tests of the Macro with the UNC's that were not being resolved AND IT WORKED!! I Love America!! What a country! Where even the unclean can fix a problem that never should have existed!

    Anyway, I hope this helps the next person that does a search on UNC problems. And Good Luck to you!

  8. #8
    Plutonium Lounger
    Join Date
    Nov 2001
    Posts
    10,550
    Thanks
    0
    Thanked 7 Times in 7 Posts

    Re: Macro path definition prob. (MSWord 2000/ WIN XP)

    Thanks for sharing this. The steps you went through sound very logical and well thought out.

    The F$ and G$ shares are hidden "adminstrative" shares that are created automatically by Windows so that people with Administrator access can get to the disks even when you haven't explicitly shared them. This is completely normal.

    StuartR

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •