I just got in so if you cleared it I did not see it and I will not open of I see an un-replied from you before this. Besides my UT client is acting up - no left menu panel.

I don't know anything about any "Quay" situation - as far as I know - with a bad-a like you in their corner - they should be doing pretty good. I was just jibbing your hard earned efforts to convert the vfp to net - and now I just noticed that there is no "Quay" in your message header.

It was a "swipe", a "provocation", a "snide" remark - but it wasn't personal.

First - and maybe a lot of us are like this - we enjoy project work we enjoy design - we like building cool programs - we like competing - competition fires the desire to aspire! Say it again, reverend! Developers can sense their progress on the road to perfection. Our last project was a little better than the one before. We learned to do this or that! We learned trickier business rules. We did something brand new - like babes in a candy store! Frank Loyd Wright designed Sears and Robuk "kit" houses before he did his famous stuff. Developing doesn't break bones. Baby boomers under-bread - we will need to stay on top and be flexible for a long time to come.

I am not saying we will all be FL Wrights - but we can never be an FLW if we don't press beyond our limitations. Move the bar or die! Right? What are the options - be medocre? Am I enough - can I succeed? Or, am I not enough and too simple to realize I can never succeed? Regardless of how that question is answered the only outcome is to continue to press for success.

There are no limitations in this business. However achievement is gauged - it is a measure of the individual's desire to be a success. It is not something a messianic wish will bring - it's practice - it's taking risks - it's being honest.

So many disciplines - the tool set - communications - zen - focus - code, code, code or learn to live in a van down by the river.

Here are the issues:
We are developers (professionals) - not technicians (custodial). Our careers should overshadow what ever is in our toolbox because we are professionals. We are not the "Xerox" guy - not the "VFP" guy, not the "NET" guy - maybe the "shrimp burp" guy. Who here works for Microsoft? Are we MS "tool" technicians? Or, are we professionals and we take our own path and we work for ouselves. We are our own man, man! I am not man bent on doing a monkey's job - no ill intent to monkeys. Say it agaaaaiiiiin! Do you feel ? Do ya feel it? Way down inside - Way way down inside - aaaaaaaaah!

Duh Duh Du Du Duh Du Duh Duh Duh Du Du Duh Du Duh!

We are pros because we love our work and deep down inside every f_ing one of us is a little demon that wants to rule the world. Code - code - code or ... you'll never have a girlfriend you won't have to pay for! Praise be - Praise be - don't let that happen to me!

We would push to write the best programs we could regardless of the tool. We are not "technicians" - we are not software "janitors" - we are beyond "tool" affiliations - we are developers - we are textual designers and we have burned the candle to puss to acquire our expertise.

Now we sort the wheat from the chaff - there are two kinds of demons in this business - the kind that want to rule the world and the kind that want to have a corner office.

The kind that want the corner office never rule the world. They become administrative assistants to those who do rule the world.

Are IT seminar and IT book authors lagging the "purer" development community becuase their "information marketing" vocation consumes mass amounts of coding time. It's easy to keep the balance on a bicycle - but if you don't ride everyday - you'll eat the dust of those that do! Jo `le!

The other issue is tool.
What can you do with the NET GUI that I need to do with a mom and pop that does not want a DBA? Set that aside. VFP can mimic any attribute you assign to theNET GUI tool sets. VFP with passtrhough and stored procedures on a SQL back end is bad! It kicks!

There's really no advantage of one over the other. The neat thing about the discontinued VB was that VB had such a small footprint it was easy to download and evaluate their projects. I have seen and been inspired by some great VB projects and great VB developers. Who want's to spend the nite downloading a NET "yield calculator"? Takes all the fun out of it.

There is no difference - it doesn't matter - but the adverserial - the plans (convert your vfp app to net! tah da daah) - is microsoft paying people to behave and talk that way?

What should MS do. Package each "tools" script enging in an OCX. A VFP one, A C++ one A VB.NET and maybe VB. The the developer could just drop them the app container and address theorgh a container hierarchy.

The VFP container could reference the NET containers name and once that was done - the VFP app could drive net from the VFP container. The same with NET. Certain VFP data ops are fast. The NET container could refrence and script VFP code.

Burt first MS has to commit to make VFP 64bit - do it soon - sell a bunch of the new 64 bit desktops - move some refrigerators and microwaves on your M-TV.


>I edited my last question, but not in time....
I did n't see it - was it really nasty - did you make fun of some double secret "tick" you've observed in my personality - if you tell me - I can probably save thousands on therapy - let me see what the doc looks like first.


>
>What first-hand specifics do you know about the Quay situation?
Duuuuuuhhhhhh - But I love gossip - tell me tell me tell me please!!!
>
>Kevin