Let me set up the situation.
I have a VB6 app running from a network share. Users access the EXE through a short cut on their desktop. The EXE automatically accesses it's INI file from the same directory where the EXE lives.
What I need to be able to do is to allow the users to have their own individual INI files on their workstations for this EXE.
Is there either (1) a way I can program in my VB6 code to access the shortcut's "Start In" path, or otherwise (2) direct the EXE to look for the INI file on the workstation rather than on the server where the EXE is running from???
Stay Cool Ya'll!![[smile2] [smile2] [smile2]](/data/assets/smilies/smile2.gif)
-- Kristin
I have a VB6 app running from a network share. Users access the EXE through a short cut on their desktop. The EXE automatically accesses it's INI file from the same directory where the EXE lives.
What I need to be able to do is to allow the users to have their own individual INI files on their workstations for this EXE.
Is there either (1) a way I can program in my VB6 code to access the shortcut's "Start In" path, or otherwise (2) direct the EXE to look for the INI file on the workstation rather than on the server where the EXE is running from???
Stay Cool Ya'll!
![[smile2] [smile2] [smile2]](/data/assets/smilies/smile2.gif)
-- Kristin