>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.

All languages were reviewed before the project started, and VFP proved to be the most cost-effective and would also integrate with the current Fox4Dos application (which it needs to) plus it appeared that you could develop the weird and wonderful GUI that the users wanted, easier with VFP.

The project has been going for 3 years now, to start to re-write it would just be plain illogical, especially when we haven't hit any limitations or problems with VFP and we are quite happily continuing.

I'm not saying it's always right to use VFP, but when your staff consists of 3 Foxpro developers to 1 Oracle developer - doesn't that seem strange to switch?

>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.

Well that's another thought, I AM open minded, but it's always possible that it won't be me doing the work, I've worked on Oracle DB's before, in fact my experience started with Oracle running on Unix, so i'm Ok with that.

I don't feel strongly about the use of VFP, I feel strongly that our clients think the reason the project is taking so long is down to the language we are using, which you and I know, is utter cr*p, the reason it's taking so long is down to our clients response times!

Kev