Hi Tracy,

There is no question that the existing investments in IT, (technology, skill sets, etc) is a factor. However, when architecting a solution, I would argue that at that point, one should be dealing in abstract items that are independent of a specific technology. Specifically, I am referring to business requirements, use cases, identifiable business challenges that you are going about solving, etc. I am a big fan of the MSF (Microsoft Solutions Framework) approach.

At some point, I agree that current investments may make VFP more justifiable. However, this will only work if it can work in the set of constraints that have been identified. For example, the the data size requirements outstrip VFP's capabilities, VFP may be a moot point from the start, even if the cost factors were favorable.

You defintely bring up good points and at a later point in the process, they are factors that need to be considered.

With that said, I think we are in agreement!!



>Ok, here I go again. I'm disagreeing this time John (well, actually ONLY partially). While I agree that if either he or his boss are already FIXED on a solution (VFP or Oracle) without mapping out the pros/cons they are both wrong, considering the investment the business already has in existing developers (VFP and Oracle comparatively AND against retraining either or investing in new staff) versus using any other development tool at all (regardless of what it is) is one of the major considerations in how to best meet business requirements. Of course the future availability/cost of developers in either tool is a consideration too. It's great to have the developers you need in a specific tool right now, but IF you have the ONLY developers in your geographic area in that specific tool, that does not bode well down the road.
>
>Rather a long and poorly constructed run-on sentence I know, but you get my drift. :o) I think we agree though, that there are MANY things to consider when deciding what tool, datastore, etc to use to meet business requirements and neither individual should be 'fixed' on a solution simply due to comfort or preferences.
>
>Tracy
>
>><<
>>My boss thinks Oracle is the only language to use (even though we've been using Fox since '91) and although I've tried the usual pieces of info I'm still having trouble convincing them.
>><<
>>
>>How is this different from the person who thinks VFP is the correct tool all the time? The fact is, if you are undertaking a new project and have already settled on a particular tool, you are BOTH wrong. You should design and architect a solution INDEPENDENT of a particular technology. If Fox is the right tool, great. If Oracle is the right DBMS, great. If it is SQL Server, so be it.
>>
>>If Oracle presents a new opportunity for you, why not be open minded about it. The fact is, the political cards may already be stacked against you. If you feel THAT strongly about this, leave. Otherwise, you should probably look at the positive angle that provides an opportunity for you to expand your skill set.
>>
>>
>>
>>
>>>Hi
>>>
>>>I know there have been some people who have had trouble convincing their boss(es) that VFP is a perfectly acceptable programming language and that MS are supporting it.
>>>
>>>My boss thinks Oracle is the only language to use (even though we've been using Fox since '91) and although I've tried the usual pieces of info I'm still having trouble convincing them.
>>>
>>>Anyway, could anyone advise me the best way to tackle this, has anyone else had this problem?
>>>
>>>Thanks
>>>Kev