>>>>>>Since I moved my development to a new computer, the folder names are not 100% matching, I need to hack all my VCX libraries. I am obviously concerned that I don't mess up something. So here is what I am planning to do and wanted to know if anybody sees any potential issues with this. I am creating a .PRG that will do the following:
>>>>>>
>>>>>>

>>>>>>*-- for every .VCX in the director. And in my app all libraries are stored in the same directory/folder
>>>>>>cOldLocation = "c:\folder_on_old_computer" 
>>>>>>cNewLocation = "d:\folder_on_new_computer" 
>>>>>>use (cVcxFileName)
>>>>>>REPLACE classloc WITH STRTRAN(classloc,cOldLocation,cNewLocation) FOR AT(cOldLocation,classloc)> 0
>>>>>>

>>>>>>
>>>>>>I know that there are tools for this type of thing but I don't have them and need to get done asap. TIA.
>>>>>
>>>>>I don't see a problem here. Of course, you need to keep backup copies of your VCX.
>>>>
>>>>Yes, of course I will make a back up first. Thank you for checking my code.
>>>
>>>Actually, the classloc usually saves relative reference so you should not need to change anything assuming you keep the same project structure.
>>
>>Funny thing is when I was checking a couple of .VCX some entries in CLASSLOC were relative and some were absolute. I think it is possible that it was my fault. Some years ago I moved my development and was probably hacking the libraries too. Do you think I should change my code (above) and update the locations with relative folder names? Like "..\libs\" instead of "d:\folder_on_my_comp" ?
>
>Yes, better to keep all references relative than absolute.

Thank you. I will do that.