Hi Al,

>I'm meeting soon with a client, after which I'll be asked to prepare a quotation/proposal. Can you suggest any questions/subjects I should bring up at this meeting to facilitate this?
>

Are they going to pay you for your time to do this? Or have you made it your business decision to do RFPs on your own time and dollar? Do you know if they are getting RFPs from other developers?

>- Client currently has a functioning product written in FPD 2.6. This is a very narrow niche product, total market potential is between 50 and 100 sales. Currently 3 sites are using the FPD version and are apparently happy with it.
>
>- The product is "semi-custom" - most of the functionality is the same for each customer, but there have been customizations made for each as well. It is likely that at least some of any new sales will also require customizations.
>

This is a good reason to take it to the OOP level. Evaluate the existing app to see where it is consistent then the "customizations" become easier.

>- The existing customers have "expressed interest" in upgrading the product to a Windows version, however, they are not willing to help fund this process up-front. A developer working for my client has mostly completed a rewrite of the app in VFP5 using the CodeBook 6 framework. At the moment, ownership of this work is divided between the developer and my client.
>
>- The developer has become permanently disabled with carpal tunnel syndrome and physically cannot complete the project; he wishes to cash out his interest in it and exit the profession entirely. However he will be available for consultation until this project is complete. My client would like me to take over this project and complete it so they can start to market it. They are open to straight pay for work, an equity position in the product, or some linear combination.
>

You might want to speak with an attorney on creating deriviative works. The original developer needs to give you written permission to work on his code to create derivative works. You may also need to get in writing that the original developer is cashing out and what is gets is what he gets. If the product becomes a "money maker" will he be able to come back and ask for more?

Is this other consultant going to be compensated for his time. If so, by you or the client?

Bottom line: Set everyone's expectations up front. It doesn't have to take an attorney (but they are the ones who know the laws, and how to keep you from problems) to get involved, but as long as there is some kind of written agreement between everyone, everyone agrees and signs it.

>- I am not familiar with the CodeBook 6 framework and would not use it on any other project (would use VFE6 instead). The developer is willing to consult on this issue as well.
>

When you say he is willing to consult on this issue. What does this mean exactly? The fact is, you are not familiar with CodeBook 6 so, is he going to train you in it? On your own time? Does the client know about your lack of knowledge of the framework the developer used? Is the client willing to take you on knowing this? How are you going to write a good RFP if you are unfamiliar with the framework?

>If anyone has had experience dealing with this sort of situation I'd love to hear about it!

Do you need this contract? When meeting with this client what are your gut instincts about getting involved with them and this project? What about your gut instincts with the other developer? He is saying one thing, does he really mean it? Follow your gut! It's been my experience that when I haven't followed my gut, I should have.

I know I asked a lot of questions, but have you asked them of yourself?

HTH,
Jacci