They are, however, available at run-time. So the actual Set ClassLib code references the classes with relative paths but the windows file system returns explicit paths to the fox run-time and the runtime uses the explicit files names to open the libraries and that's what we see here.


>I dumped the classlib definition into a text file. This gives this:
>
>

>D:\WWW\CLASSES\WWMSMQ.VCX ALIAS WWMSMQ
>D:\WWW\CLASSES\WCVISUAL.VCX ALIAS WCVISUAL
>D:\WWW\CLASSES\WWIPSTUFF.VCX ALIAS WWIPSTUFF
>D:\WWW\CLASSES\WWXML.VCX ALIAS WWXML
>D:\WWW\CLASSES\WWSQL.VCX ALIAS WWSQL
>D:\WWW\CLASSES\WWBUSINESS.VCX ALIAS WWBUSINESS
>D:\WWW\FOURNIERTRANSFORMATIONLISTE.VCX ALIAS FOURNIERTRANSFORMATIONLISTE
>D:\WWW\FOURNIERTRANSFORMATION.VCX ALIAS FOURNIERTRANSFORMATION
>D:\WWW\UNIVERSA\UNIVERSALTHREADMASTER.VCX ALIAS UNIVERSALTHREADMASTER
>D:\WWW\UNIVERSA\UNIVERSALTHREADLIST.VCX ALIAS UNIVERSALTHREADLIST
>

>
>But, this is from an EXE. Those paths are also not available in production. So, how does the SET CLASSLIB able to interpret all this?