>Hi Kevin,
>
>I think you have made great effort to convince your managers to stick with VFP. However, developers better than you and me have lost this battle before. At a certain point, we have to stop trying to convince those that will not listen, and decide where our careers should go.
>
>I know it has been mentioned before, but is there a way you can remain involved with the project? Could you offer suggestions for migration, possibly making use of existing code? You likely know more about this application than anyone else. Shouldn't they make sure you are involved with it?

Well, that's what I have to hope for, and luckily for me it will probably be the case.

We are pushing for a VFP front-end with a Sql-Server/Oracle back-end. What I'm trying to stop is the Oracle front-end for 2 reasons:

a) The application is seriously complex (it's 3 years in development and only 50% complete)
b) I "like" programming in VFP, I think you can achieve things quicker than in VB/Oracle

Of course if the worst case scenario were to occur, then I may be re-trained - which I don't mind, but I hope I won't be pushed aside.

>I think it may be time to go along with their decision, otherwise I fear you may be hurting your job security. The best developers don't shy away from learning to use new tools, and Oracle doesn't look bad on a resume.

Like I said, I certainly wouldn't mind - least I wouldn't have the same old FoxPro questions over and over :)

Thanks for all your comments, they are appreciated.

I'm probably fussing about nothing - I normally do.

Cheers
Kev