P
phreud
Hi all,
I'm using the package and deployment wizard to make an install CD. When
adding the .ade file, I specify $(AppPath) as usual. Everything works
fine when installing, unless I choose to install to another (not
default) disk. If I install to another disk and try to run the program
from the startmenu, it can't find the .ade file.
I checked the shortcut created in the start menu, and it references the
Access application with it's full path. I guess the .ade file specified
is relative to the access path!?
For example, the shortcut created might be:
Code:
--------------------
"E:\Some\dir\where\access\is\located" my_file.ade
--------------------
My guess is it's looking for the .ade file in the same dir as specified
for access? I might add that I can't assume to have write permission to
that dir in future installs.
Any thoughts?
Thanks in advance!
I'm using the package and deployment wizard to make an install CD. When
adding the .ade file, I specify $(AppPath) as usual. Everything works
fine when installing, unless I choose to install to another (not
default) disk. If I install to another disk and try to run the program
from the startmenu, it can't find the .ade file.
I checked the shortcut created in the start menu, and it references the
Access application with it's full path. I guess the .ade file specified
is relative to the access path!?
For example, the shortcut created might be:
Code:
--------------------
"E:\Some\dir\where\access\is\located" my_file.ade
--------------------
My guess is it's looking for the .ade file in the same dir as specified
for access? I might add that I can't assume to have write permission to
that dir in future installs.
Any thoughts?
Thanks in advance!