First the background: We are having a two phase development effort in moving our FPW2.6 application to VFP6. The first phase is more of a migration of our existing code, screens and reports. The second phase will be new development using Mere Mortals as the framework. Our current 2.6 application runs with the Codebook framework.

For this initial migration of our FPW2.6 stuff, we have modified the VFP Convert App to convert/migrate our 2.6 screens with some specific attributes (over and above the way that the standard Convert app works). Part of this involved using some of our own base classes for the forms - during the coversion, we have the Convert app point to one of several forms that exist in a class library.

The dilemma is concerning how we can successfully deliver the migrated forms to the customer. We want to continue sending out the .Scx/.Sct files and do not want to place the forms into a project. We are encountering some problems because the forms are looking for the class library in a specific place, say "c:\Application\libs\myClass.vcx" and our customers are allowed to change the drive (and even some of the directories) when a system is installed. We have tried to use some relative pathing, but this does not always work and when the Form is run the Locate Class Library dialog appears.

Does anyone know of a solution to this problem?
Thanks...douglas