Variable in Priority Path?

[Darryl]

Are you sure that you have MSTAR32 set up as your %AppDir%? Are you sure that you are installing the files to the MSTAR32 directory?

------------------
Sincerely,

Darryl Hnatiuk
Indigo Rose Corporation

[VictorReinhart]

Re: Variable in Priority Path?

<>
Yes. %AppDir% is "C:\MSTAR32"

<>
Yes. I even checked the box to let me search for my file (wo.db) if SF could not find it, and it opened the Search for File dialog box. I also displayed the value of my variable: %AppDir%.

However, when I hard-code "C:\MSTAR32" in the Priority Path, SF finds my file.

It seems that SF does not "expand" my variable %AppDir% in the Priority Path -- perhaps it is just using the literal value.

TIA for any suggestions.

[VictorReinhart]

Variable in Priority Path?

I want to warn my user "up front" that he will overlay his database file. (Not wait until much later).

In Settings, Variables, File Search Variables, I type a Priority Path of
%AppDir%. However, Setup Factory does not find my file, even though it exists. If I hardcode the Priority Path to C:\MSTAR32, then Setup Factory finds my file.

This is important, since my user may change the value of %AppDir% beforehand.

Any suggestions?

Thanks in advance.

VictorReinhart



------------------
VictorReinhart

[Mark]

Re: Variable in Priority Path?

Hi,

You might as well hard code the path because the File Search occurs when your installation initializes. So there is no point on using a variable, since the user can never change its value anyways.

mark.