>>>We are installing a new program on a customers Win 95 machine which was created via setup disks. We use the line
>>>set library to ADDPROP5
>>>in our code. After the installation, the fille addprop5.fll does exist in the root directory where the exe resides. Yet we get a message indicating that it cannot be found.
>>>
>>>Do you have any suggestions of what might be going on here?
>>>
>>>Thanks much,
>>>Nancy
>>
>>You probably have to include an explicit path in the "SET LIBRARY" command. Since your install probably allows the users to choose their own install directory, you need to have a routine in your code which will determine the program directory at run-time. I believe the function to use for this is SYS(16,0), but I don't remember for sure, and I'm not at my own computer to check on it. I know that you have to do a little parsing to strip off the program name so that you get only the path. It's something like:
>>
>>lcProgName = SYS(16,0)
>>lcProgDir = LEFT(lcProgName, RAT("\", lcProgName))
>>
>>And then you can:
>>
>>SET LIBRARY TO &lcProgDir.ADDDROP5.fll
>>
>>It's generally a good idea to establish the program directory at startup and save it to a global variable (or as a property of your application object, if you're using one).
>>
>>If you don't want to recode and recompile (and rerun the setup wizard, etc.), you might try simply putting ADDDROP5.fll in the windows system directory. I think the program will be able to find it there. This is not a good practice in general, because there are rules you should really be following if you're going to make use of publicly used directories. It's not very likely any other application is going to be looking for a file called ADDDROP5.FLL, but it's theoretically possible.
>>
>>Hope that is helpful.
>

I will go ahead and answer my own question just in case someone finds something similiar.
It seems that some of the older systems do not have the file msvcrt.dll. We loaded a copy of that file from from my copy of the Vfp/distrib.src/system directory and the problem was solved. At least it was solved on two of the computers on which we had this problem. We will try on the customers site today.
Thansk much,
Nancy
>
>Thank you Mark,
>
>Yes I have all the correct paths set, etc.
>
>It appears that we needed a file called msvcrt.dll and that sometimes does not exist in an older machine. We were able to create the problem on one machine and correct it with this solution. We are in the process of now testing that fix in the field. If it is a correct solution, I will post it for everyone's information.
>
>Thanks again.