>We used to manually install the correct "drivers" at the customer. I have decided that it is easier to include all drivers in the product and then allow the user to select which bank he uses.
>
>The problem is that this is going to really clutter up my project. If this were VFP, I would create a separate project and a dll, I suppose. But I use FPD 2.6. What do you all suggest. Normally I prefer to have a huge monolithic exe file, so everything is always sinchronized.

You have several ways to go... one of them is to have an installation-dependent driver name somewhere (in config.dbf) and call it from a name expression, like

do (lcDriverName)

This way the project manager won't find the driver's name and it won't get cluttered this way. You only have to make sure the driver *.fxp files are shipped and installed, and visible in the app's path. This was the way we shipped user specific stuff in FPD - the difference was that we had one specific .fxp which was created for each customer, but it was marked as excluded and it was shipped outside the .exe, so we didn't have to rebuild each time. I guess that's what you wanted.

HTH