>Hi all,
>
>I raised this a month ago but just now cycling back to it. Users would sometimes get a couple errors after they have opened their DVD drive (Drive D:) and then closed it. The error would occur when opening a new form after reading something from the D: drive and then taking out the CD (the last step is important - does not happen if they leave the CD in the drive).
>
>The error is "error reading from drive D:....retry, cancel" etc. They can get by it by clicking Cancel two or three times.
>
>I think I tracked it down to the fact that on my dev machine, all the code is on my D: drive.
>
>I put in some test code to output DISPLAY STATUS to a file.
>
>The one thing I noticed in the output file is that there is still pathing attached to classes loaded e.g. here is start of the line from the display status file:
>
>Class libraries: D:\VMP\XLIB\XXFW.VCX ALIAS XXFW, D:\VMP\XLIB\XXFWUTIL.VCX ALIAS XXFWUTIL, D:\VMP.............
>
>So it seems the compiler is leaving the pathing in and then when the user uses the CD drive, it continues to try to search it.
>
>Is it how the SET CLASSLIB TO xxx ADDITIVE is being called or is this a VFP problem? (the code that loads required classes is within a framework so cannot just change that).
>
>Albert

Hi Albert

Visual MaxFrame Professional (VMP) includes a utility to remove such pathing. DO XXDTXRelPath