oRox,

>>Don't waste your breath. John wasn't around when you had to teach power users the "dot prompt".
>
>uhhhhh.... excuse me? I had to teach users & managers & < gulp > even customers once, what the "dot prompt" was. And John's older than me. So pick another angle.

Yeah, except that you may be smarter and have been doing this longer than John. He was a 'newbie' in the early 80's by his own admission to me several months back. That was when he remarked to me about how folks like Tom Rettig, me and others helped him out. He's way smart and has gone far beyond what I've done and I applaud him for it but that still does not remove from him the responsibility for good social graces I'd imagine. Besides, you're too young to compete with us old fogeys... <g>

Ask him how many years he's developed with Fox products...... I will - John, how many total years have you written FoxPro code? An aggregate if you would please. I've been at it for close to 14 years solid. I think Craig's been at it for about 16 or so.

>
>Just for the record, since I piped up here, yeah sure I experienced several shops where dBase and occaisionally foxpro for DOS was implemented as an end users tool. BUT - this was before Microsoft bought the product, and before Excel was what it is today. In fact I remember preparing written justification to use foxpro for DOS as an end user tool because LOTUS couldnt do variable driven comparisons. The justification was excepted by management, end users used the foxpro with USE/BROW/APPEND instructions for approx. 9 months until I got my first fox app written. So it was a temporary fix where it was used as an end user tool, not a long term one. But we're talking dark ages here folks, the days when nobody even knew what a gigabyte was. I dont see how that's relevant to Access being stated as the logical upgrade to fox 2.x. Personally I think that stupid chart should state VFP as the logical upgrade, but then again if you need a chart and can't analyze your own requirements... maybe
>you should use Access.

AGreed.. The chart should have pointed to VFP and this stupid thread would have never existed.

>
>And while I'm on the soap box, all these discussion today seem like more of a testosterone match regarding who can out argue who and to hell with what technical points are being argued.

Oh yeah?!?! Says who?!?!?

<g>

> Take a step away from it boys, and the whole VFP chip-on-the-old-shoulder is sooooo apparent up here today it's almost clausterphobic.

Nahh.. I think it's the "we're a little tired of only seeing JVP around here when he a) needs to diss VFP & promote himself via his better analysis, experience, wisdom, logic etc and b) ditto #1. <g>

> Ahhhhh but wait, I think John already stated today that it's that usual attitude that causes such a limited perception of certain things in this community... < smirk > nebbermind :)

Not so oRox. That's a gross generalization. I'd say that if VB is the better product for your needs, use it. If SQL or Access or VFP or Delphi or Excel or [you fill in the blank] is better, then use it! Just quit wasting the bandwidth using your presumed higher knowledge with stupid exerciese.

You are correct that folks are more than a little 'twitchy' about the issue. Having said that, have you noticed that there have been other folks asking essentially the same question without the same reaction?

Hmmm... Wonder why....

Personally, I think JVP was bored and wanted to get everyone here all riled up for his own amusement. <g> In that sense we're entirely predictable. <g>

Best,

DD