Sorry for the confusion.

Let me paint the entire picture...

The main focus of the work that my department undertakes is to update our main data tables with client provided input. This involves converting raw data from many different sources received in differing formats and data type (txt, xls, dbf, cvs etc) into a common system data structure. As you can imagine, each client has its own set of rules that must be adhered to when converting their data. So, in an effort to standardize as much as possible, I designed unique "environments" for each client to work within. These "environments" are initiated when a user double clicks on the shortcuts previously mentioned. The shortcuts contain a unique config.fpw for each client. Each config.fpw is responsible for setting the path, the default directory, unique menus etc. As stated, I have done this to help facilitate a standard working environment for our programmers. I am also in the process of developing an application that will eventually do away with the shortcuts, but it is not yet ready for publication. I store these shortcuts on a shared folder that resides on one of our servers. That server is running win2000. The problem surfaced when one of the programmers, who works on a pc running win2000, could not run any of the shortcuts. I checked out the properties from this users workstation and found that the target did not resolve to "c:\program files\microsoft visual foxpro 8\vfp8.exe" -cr:\convert\client folder\config.fpw. Instead it showed "c:\progra~1\micros~1\vfp8.exe" -cr:\convert\client folder\config.fpw. However, from another winXP workstation, viewing the properties of the same shortcut, revealed proper target resolution. Further checking on other win2000 workstations revealed that they also failed to resolve correctly. Hence my situation. Those of us using winXP have no difficulties, those on win2000 do. Additionally, if I create the same shortcut from a win2000 workstation, on the shared folder, it resolves correctly for all users, win2000 and winXP. It is only when a shortcut is created on the shared folder from a winXP station that the win2000 pc's fail to resolve. I have posed this problem to our in house help desk and they have yet to find a solution. I have scoured ms knowledge base as well and could find no mention to this particular behavior. I can create any needed shortcut from a win2000 station, but I am curious to know what is causing win2000 to fail to resolve a winXP created shortcut. As previously stated, all programmers have VFP8 installed on their local hard drive, so it is not a situation where the os doesn't know where to locate it. All the VFP installation were to the default directories so everything is as it should be. I have verified this also.

I hope I have clarified any miscommunications from my earlier posts.

TIA
Vince