>ADO sounds even worse, and worse yet is the impression I've been given here >that ADO is to be THE ANSWER to all woes. If its strength is datasheets and >such, and it essentially paralyzes database fucntionality, then we may be >being sold another BILL of goods (pun intended)!


Jim,

I am afraid to say that much of Bob's comments to you are inaccurate with regard to ADO.

Is ADO a panecea? Of course not. There are several issues facing VFP developers that can make it difficult to implement. Specifically, the ability to surface events, ActiveX Data Binding. Does this mean ADO is totally worthless? No. Is ADO just like ODBC? No. If you or anybody things that - I suggest reading up on just what ADO is.

At certain times, ADO, paired with native VFP data access, can be very powerful. For example, have you ever wanted to pass a cursor as a parameter to some proc/function/method???? Now you can - with ADO. If you ever needed to pass chunks of data to a COM DLL, you can with ADO. If your VFP COM DLL, needs to serve data up to a variety of clients- you can with ADO. Or, if your VFP app needs to get data from a VB app, it can with ADO.

Sorry, but it really stokes me when folks run at the mouth - bashing a technology - when by their own words - don't know crap about what it is they are talking about. To me, that does quite a bit of damage to the community. Once again, I keep harping on the accuracy thing. You may have seen it in another thread<s>.

To all: If you are going to bash something, please take time to get the facts before bashing. Many folks make evaluations based on what they read here. Best that it be as accurate as possible.