Thanks, my issue is why convert the virtual path to a hard coded one, it defeats the purpose of these Special Folders. My %HOMEPATH%\My Documents is on E: drive today and maybe I: drive tomorrow, but any program maintaining the Special Folder path won't need to know that or care. Now due to different versions of Windows, maybe that is harder to code for or won't work on a MAC.
This comes from the Wikipedia definition of "My Documents"
Note that "My Documents" in these operating systems is one of a number of Special Folders - a concept introduced in Windows 2000 to add a layer of abstraction between the user interface's presentation of the folder and its physical location and contents. As such, "My Documents" in file load/save dialogs (and in Windows Explorer) doesn't appear as an absolute path. A user can change the physical location of "My Documents" by right-clicking on the "My Documents" icon, selecting the Properties option, and entering a new folder location (path) in the Target tab.
Windows Vista renames "My Documents" as, simply, "Documents". "My Music", "My Pictures" and "My Videos" have also lost their prefix, and have moved to directly under the user's profile directory (C:\Users\[user name]).
As of Windows 7, The "Documents", "Pictures", "Music" and "Videos" folders appear displayed in Windows Explorer with a "My" prefix but are actually still stored in the file system without the prefix (as in Windows Vista).
An application can convert environment strings in a user-supplied path (e.g. "%HOMEPATH%\My Documents") to an actual path by (for example) calling the function ExpandEnvironmentStrings.
Windows 7 Ultimate 64bit
Velocity Micro
Intel Core 2 CPU 6700 @ 2.66GHz
RAM 6GB
NVIDIA GeForce 8800 GTS v258.96
ViewSonic VX2255wm-4 dual extended display
K-Lite 32bit & 64bit
1680x1050
Windows 7 Basic background no Aero
Hitachi 400gb system dr