Hi All,

I'm after some advice on the best way to implement something.

I have an old legacy system which I am looking to upgrade to VFP9. The old system was orginally written in 2.6 then ported to VFP6, the client base required that significant bespoke work was required to the system and this was handled by having the 'Standard' system which was all contained within a single executable, the bespoke work was distributed by sending spx (form) and fxp (program) files to the customer and meta data flagging that the system needed to run a different version of the form or program. The forms were run in compatibility mode and built from the spr so they are not forms as such. This has worked well for a long time but I am now moving the code into vfp9 forms, this has worked really well for the standard forms but I am not sure of the best way to deliver the individual customisation.

I think I have the follwoing options:
Build the bespoke work into the main executable - we have over 300 bespoke systems and this would increase the overhead to our support team.
Distribute the scx,sct files - can be editied by users.
Wrap the bespoke forms into another FoxPro exe and run the forms from within that environment. - This is the way I have been trying to go, but am running into some issues with this.

Are there any other\better options for trying to achieve this?

Is this actually achievable?

Are there any resources\articles that can point me in the correct direction?

Thanks in advance for any replies.

Jon