>As for relative paths... I am not using exactly relative path like
>(currentfolder+) .\somefolder\somefile.xls
>which depends on current folder, it is always kind of 'beheaded' full path; whole path without drive letter prefix
>which naturally is not known prior deployment of app.
>
>So instead of using
>c:\rootfolder\subfolder\subfolder\subfolder\file..
>it is always
>\rootfolder\subfolder\subfolder\subfolder\file..
>
>And it always worked, in all versions of office so far. Except in my new VFP IDE on my new machine with office 2013.
>Again on other machine that also has W7 + VFP9 IDE + Office 2013 - no problem.
>
>Only on THIS (new) machine. Will actually try making another virgin installation to see if it happens again or is
>just bizarre set of circumstances causing it to happen.

On which disk?

I assume Office and the file were always on the same disk, and now you put them on different disks and they can't find each other. And it doesn't really matter if you installed office on w:, a COM object may as well have c:\windows\system32 as its current location, or perhaps the %appdata% folder. You don't know, and you shouldn't care. Full path when talking to strangers, always.


With proper full paths it doesn't matter if they aren't on the same machine - UNC is also a full path.