>That may be your reality and I respect that. However, I have been asked to quote for an application that is for the same business space in which I delivered another very similar application in VFP a few years ago. Whilst I could use either tool (VFP or .NET), I wouldn't actually dream of using VFP. Notwithstanding my personal preference, this proposed new application will replace one that was originally written in Clipper and migrated into Xbase++ (when they wanted to get into Windows from DOS). The client has insisted that I develop this application in .NET/SQL server. Their reason for this explicit instruction is not technology based. It is based on their experience of the difficulty recruiting Clipper and then Xbase++ developers. They want to use perceived industry standard technologies where there are a wealth of developers available from a large talent pool. This analogy equally applies to VFP - one of the reasons that my current job is based on C#/.NET is because the business
>found it extremely hard to recruit VFP developers.
>
>So, I guess from your client's perspective, your $15.00 hammer could prove more expensive in the long run if you become subsequently unavailable to maintain their application in the future and they have to start all over again with another new system redeveloped using a different technology. I assume that you are able to secure more than $15.00 per hour - if not, this may prove be a self-fulfilling prophecy :) Obviously, I sincerely hope not.
>

Hi Garry,

What kind of client inssist 'NET&SQL' ??? I simply cannot understand
that. Only time I ever heard something like that is in VFP vs NET threads here on UT. Never in real life.
What I always heard was ; 'We want solution yesterday! - tmrw latest.' :))

It might make sense if it is huge enterprise, WEB based, distributed app we are talking about, or if your client is actually software vendor who wants to make additional money on selling SQL licences to his clients.
Otherwise I don't see how he can possibly benefit from having to pay - much much more.

In my world (shipping) most of top managers don't know, or want to know what platform or technonlogy is used. My boss calls it 'faxpro', that word is all he care to know, and don't even think of underestimating his nteligence!
'Can this be done? / When?' Is all I ever heard.
Then you take responsability(!) - and develop/implement solution you see best fit!

Now, I would personally feel like cheat, If I told them ;
- Has to be NET & SQL
- It will take 1 to N+1 persons/years to develop
- Will cost us $$$$$ in SQL licences only

instead of

- Will take 3 months (on average) to develop and another 3-6 to fully implement/debug/round up.
- no additional costs (except eventually purchasing latest VFP version)

Regarding VFP programmers, I don't se that as good reason either.
When u hire guy/girl fresh from college, they are mostly dumbsters knowing
close to nothing (except basics), then you pick one who show some common sense / willingnes to learn - and then you teach them best tool for
most of the jobs :))

Regarding rewrites, if written well - solution will last long enough to pay back the cost of dev./implementing. Meny people still run FP4DOS programs written some 15 years back if not more. So I cannot foresee anything stopping my VFP app written few years back, riding comfortably another 20-25 years. By this time, God knows what is gonna be available outthere. We will cross that bridge when we come to it.

That is my standpoint as IT-Mgr in shipping industry, so I alow that
things might be different ,then if you are software company or consultant competing for large corporate clients in US or UK.

Perhaps, since I cannot do it, I would hv to hire or partner with some hyper-talented B*llS**t artist, to please their IT-seinsitive ears with HQ techno buzz, but I would most probably still do things in VFP :))


As Developer, I really wish that I EVER had task that REALY required
usage of assembly language or C+ or NET.C# nowdays. I would be realy happy to jump into those *tough-guys* languages :) Somehow I was always managed to develop what I was hired for with some xbase flavour. (VFP being the best ever)

BTW is there any Skin4VFP written in NET ?