calling C script from vba calls wrong executable..

[Guest]

Ok this is a bit strange. I have generated a conversion tool in ACCESS at my
development PC that exports a given table to a text file in the same
directory as my ACCESS program. Then I have Access via vba to call the
executable script to generate files from that text file and place them in a
particular directory under the current directory where the Access program
resides
C:\Conversion Tool\eDLPI - The Access program
C:\Conversion Tool\flat.txt - the text file exported by Access
C:\Conversion Tool\conversionTool.exe - the C script which generates the
files
C:\Conversion Tool\output\ - the directory where the generated files are
moved to

my problem is that another developer is taking care of the conversion tool.
I have set up all the tools necessary on his PC (ACCESS, and MS C developer)
same as in mine... and made a folder structure exactly as mine under his C:\
drive. but the clincher is that when I have everthing in his computer loaded,
recompiled, and running.. it crashes. Access wants to open files located under
C:\My Documents and Settings\<user name>\ directory.. I have checked and
rechecked all calls to where the directories are and all point correctly
C:\Conversion Tool on his machine...

any ideas?? I'm at a loss.. and any help is greatly thanked in advace!!
feel free to ask if more info is needed...

 

[Guest]

After tinkering for a while I found the answer!!
if you look under "tools" then "options" then the "general" table you will
find an option: "Default database folder" this folder needs to point to where
everything needs to be.. when calling a shell from access whatever this value
is it will be passed to the shell regardless. Hence my executable was opening
but it was having parameters passed through the shell.. weird.. anywho this
solved my problem since I changed it to C:\Conversion Tool vs C:\My Documents
and Settings\username...\

hope this helps someone if they come across it as well..
tootles