FLL install directory

Hi,

Where should I install an FLL file.
I usually install it in the program directory.
On a new app when I changed the default directory the exe reports that it
cannot find something.
If I copy the FLL to the new directory then the program works fine.

What do I do wrong?

Demetrios, Greece

Josh
Wed Dec 01 23:03:27 CST 2004

you should install it to the app dir -- that's the usual place.

You need to "set the path" in VFP so that it always finds it...



On Thu, 2 Dec 2004 06:10:26 +0200, "Demetrios Panayotakopoulos"
<dpan__dp@_ath.forthnet.gr> wrote:

>Hi,
>
>Where should I install an FLL file.
>I usually install it in the program directory.
>On a new app when I changed the default directory the exe reports that it
>cannot find something.
>If I copy the FLL to the new directory then the program works fine.
>
>What do I do wrong?
>
>Demetrios, Greece
>


---
Remove x's to send.

Demetrios
Thu Dec 02 00:42:45 CST 2004

I copied the FLL (convert.FLL) to the System32 dir which is in path but the
error reappeared.
The problem may be in a freeware VCXs that I use, which probably uses the
FLL, and which expects to find it in the current directrory.

Demetrios, Greece


"Josh Assing" <xjoshx@jassing.com> wrote in message
news:tb8tq09622emi800o18n91nvr3th2lpish@4ax.com...
> you should install it to the app dir -- that's the usual place.
>
> You need to "set the path" in VFP so that it always finds it...
>
>
>
> On Thu, 2 Dec 2004 06:10:26 +0200, "Demetrios Panayotakopoulos"
> <dpan__dp@_ath.forthnet.gr> wrote:
>
> >Hi,
> >
> >Where should I install an FLL file.
> >I usually install it in the program directory.
> >On a new app when I changed the default directory the exe reports that it
> >cannot find something.
> >If I copy the FLL to the new directory then the program works fine.
> >
> >What do I do wrong?
> >
> >Demetrios, Greece
> >
>
>
> ---
> Remove x's to send.

Andrew
Thu Dec 02 02:49:23 CST 2004

Demetrios Panayotakopoulos wrote:
> Hi,
>
> Where should I install an FLL file.
> I usually install it in the program directory.

That's where I put it and I usually open it with
SET LIBRARY TO SYS(2004)+'library'

When doing this it's worth adding
EXTERNAL LIBRARY library

to the program so the project manager can resolve the library name if doing
a fresh build.

--
HTH
Andrew Howell

Cy
Fri Dec 03 17:15:42 CST 2004

Demetrios Panayotakopoulos wrote:
> I copied the FLL (convert.FLL) to the System32 dir which is in path but the
> error reappeared.
> The problem may be in a freeware VCXs that I use, which probably uses the
> FLL, and which expects to find it in the current directrory.
>
> Demetrios, Greece
>
>
> "Josh Assing" <xjoshx@jassing.com> wrote in message
> news:tb8tq09622emi800o18n91nvr3th2lpish@4ax.com...
>
>>you should install it to the app dir -- that's the usual place.
>>
>>You need to "set the path" in VFP so that it always finds it...
>>
>>
>>
>>On Thu, 2 Dec 2004 06:10:26 +0200, "Demetrios Panayotakopoulos"
>><dpan__dp@_ath.forthnet.gr> wrote:
>>
>>
>>>Hi,
>>>
>>>Where should I install an FLL file.
>>>I usually install it in the program directory.
>>>On a new app when I changed the default directory the exe reports that it
>>>cannot find something.
>>>If I copy the FLL to the new directory then the program works fine.
>>>
>>>What do I do wrong?
>>>
He meant that you need to use the VFP SET PATH command to make sure that
the application directory is on the VFP path and then the attempt to
load the fll should work fine.

--
Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com

Demetrios
Fri Dec 03 22:47:43 CST 2004

OK, using:
if _VFP.StartMode!=0 && NOT Development
Set Path to JustPath(Sys(16,0))
Endif
worked fine.

Thank you all.

Demetrios, Greece

"Cy Welch" <cywelch@yahoo.com> wrote in message
news:ys6sd.53703$QJ3.5688@newssvr21.news.prodigy.com...
> Demetrios Panayotakopoulos wrote:
>> I copied the FLL (convert.FLL) to the System32 dir which is in path but
>> the
>> error reappeared.
>> The problem may be in a freeware VCXs that I use, which probably uses the
>> FLL, and which expects to find it in the current directrory.
>>
>> Demetrios, Greece
>>
>>
>> "Josh Assing" <xjoshx@jassing.com> wrote in message
>> news:tb8tq09622emi800o18n91nvr3th2lpish@4ax.com...
>>
>>>you should install it to the app dir -- that's the usual place.
>>>
>>>You need to "set the path" in VFP so that it always finds it...
>>>
>>>
>>>
>>>On Thu, 2 Dec 2004 06:10:26 +0200, "Demetrios Panayotakopoulos"
>>><dpan__dp@_ath.forthnet.gr> wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>Where should I install an FLL file.
>>>>I usually install it in the program directory.
>>>>On a new app when I changed the default directory the exe reports that
>>>>it
>>>>cannot find something.
>>>>If I copy the FLL to the new directory then the program works fine.
>>>>
>>>>What do I do wrong?
>>>>
> He meant that you need to use the VFP SET PATH command to make sure that
> the application directory is on the VFP path and then the attempt to load
> the fll should work fine.
>
> --
> Cy Welch
> Senior Programmer
> MetSYS Inc
> http://www.metsysinc.com

Demetrios
Fri Dec 03 22:47:35 CST 2004

Hi Andrew,

The library was SET using the fullpath, but that didn't help.
I used "Set Path .." as Josh and Cy proposed.

Thanks.
Demetrios, Greece

"Andrew Howell" <ajh@work> wrote in message
news:%23UBKVvE2EHA.936@TK2MSFTNGP12.phx.gbl...
> Demetrios Panayotakopoulos wrote:
>> Hi,
>>
>> Where should I install an FLL file.
>> I usually install it in the program directory.
>
> That's where I put it and I usually open it with
> SET LIBRARY TO SYS(2004)+'library'
>
> When doing this it's worth adding
> EXTERNAL LIBRARY library
>
> to the program so the project manager can resolve the library name if
> doing
> a fresh build.
>
> --
> HTH
> Andrew Howell
>
>