>Some of our users are getting copies of there tables with a ~ in the name for example -
>
>Locations.dbf is becomming Locai~1.dbf
>
>Any idears how this could happen.
>
>We use SDT to update the tables etc.

For some reason, your system is not displaying the LFN, but instead the SFN of the file, and is creating SFNs. The most common cause of this is (1) attempting to create a file with an LFN on a volume which does not support LFNs will result in the use of an SFN; I've seen this happen on older Novell file servers pretty frequently.

In some operating systems, if the file names in a .LNK or the associated .PIF are SFNs, all file behavior within the executable fired from these shortcuts will use SFNs uniformly. Manual inspection of the shortcut is the easiest way to handle it if a small number of users is involved; you could also write a brief script in VBScript (or a VFP program that invokes the WSH objects) which uses an instance of the Scripting.FileSystemObject, and then finds the appropriate shortcuts be they on the desktop or in start menu or whatnot, for each involved .LNK, invoke Wscript.Shell's CreateShortcut method to inspect the content of the .LNK, and for each path-containing property of the shortcut, take the property value, use the Scripting.FileSystemObject's GetFile() or GetFolder() method as appropriate using the possibly short file name as an argument, and then extract the Path property of the File or Folder object, insert that into the original ShortCut property, release the file/folder object, save the modified shortcut and proceed to the next one.