>Hi stephen


>You are replying on a line from Rick, not mine.

Sorry.

>>>I'm still waiting on Microsoft to announce a new development platform where RAD and Database integration has the foremost priority. From my idealogical standpoint this is the wave of the future. I'd like to promote the sentence: "Every application wants to be a database application when it grow" to "Every development tool wants to be a database tool when it grows up". .NET in any way you put it does not fit the bill. I'd rather wait for the announcement of the tool (Microsoft has some research projects going on that are more data centric), than hastly jump the wrong ship. I'd rather jump once into the right ship.

RAD is a bad acronym. Rapid Development is usualy bad in the end. Not enough time was done in requirements gathering, Anaylists didn't dig deep enough to get to questions that needed to be answered. Instead they saw visions in their heads that 1) This is a simple app. 2) It's just a few forms and a couple of reports. 3)They don't really need anything more.

I have been striving hard at making my biz logic first without ever dealing with an interface. If I can unit test at this level it matters not if it's web/win/WS. It just works.

VFP Developers IMO tend to see the app through the interface. They visualize forms with buttons and controls for display / editing. It's kind of like they are blind and they can see by feeling. This isn't a put down, but I have woked with teams in java/xml, VB, and VFP. The VFP developers take the most shortcuts of of the lot.

Do you design by test? At the pre-set of a code phase, do you know what the manager expects for sign-off on this module?


>>hahahaha. Not ever tool plays well with others. .NET does a great job in attempting to deliver on that line. VFP can't, wont and that will be it's final pox.
>
>Where ever did I say this ?? I'm just awaiting new technology that more fits into my perception of the future. More the like of ERP/ERM systems with e.g. .NET integration (MBF), or an significant upgrade to their aquired Navision. IOW, more database oriented development platforms. Something that .NET currently is rather weak in. Therefore I'm waiting for the next generation of database driven technology. It is my pov that the single .NET platform is not there (yet).

Ok, Your waiting for another fourth gen language to take over the world? I know another new one will come along and it will replace C# for me. Which replaced VFP, which replaced Basic, ...

>Again, why do you feel a need to read something into my statements that is not there? I'm awaiting technology that is beyond the technology that now is offered, even with the public beta 2005. And in no ways I'm refering here to VFP as the perfect tool here. I KNOW that VFP has a lot of shortcommings that are better in .NET, but that does not mean I'm willing to give up my entire investment in VFP and willing to spend a lot of time rewriting and some features I really like and use in VFP (because they are hard to do in .NET). I'd rather sit back and wait what happens in the future. There currently is no valid reason to me to even think about adopting .NET development for the apps I'm building.

Ok, what is it that VFP can do so easily and all other OOP's can't grasp. I'm always looking for true differences myself.


>>.NET is great at the little stuff. Like making a picker dialouge that will showcase images instead of details or plain file names. When you get to the nitty gritty VFP won't ever do it and you only have to roll your own each and every time.
>
>Sure, but the question is if you need it ?? I don't have a lot of application for building my own controls. The ones I have will do it nicely, along with the current set of 3rd party ActiveX controls. Building database applications is something entirely different from building multimedia applications and not every database application lends itself to port to the web either. So it really depends on the application of the software.

I'm not building the control, just enhancing what is out of the box with .NET. I'm creating a picture(s) / movie tab to an inventory form. This app is for selling BIG Trucks, tractors, heavy equipment at auction. User wants to create eBay sales for stuff that doesn't sell localy. So I have to grab 5+ images for the truck. We shoot a 30 second video where the salesman over the asset shoots the footage, and talks about what the truck is. This is in a pilot phase now so we are seeing if it will reduce the # of emails about the asset. 1 freightliner listing can generate close to 100 emails from people all over. We are going to list the move off of our site starting next week.

TTFN