>>>>>I tried o=createobject( "ADODB.Recordset" ) in the VFP command window and got the message "Class definition not found."
>>>>>
>>>>>What do I need to install to be able to create an ADO recordset? TIA.
>>>>
>>>>I just tried it and it works. This is the correct syntax to use. Make sure all the required components to use ADO are installed in your workstation.
>>>>
>>>>BTW, just curious, why do you want to use ADO from Visual FoxPro? You can use direct Visual FoxPro commands to access your SQL Server data.
>>>
>>>Given the major hype re: ADO I'm curious about it. How do you use FoxPro to create middle-tier objects that can be used by various front ends? That can access various back ends? How do you separate business objects from data objects? (In all my spare time ...)
>>
>>
>>An excellent book is "Visual Basic 5.0 Business Objects", Wrox Press ISBN
>>1-861000-43-X. Yes, I know it says VB, but all the theories apply to any language. If you are an MSDN member, you can get this book at a discount. (www.microsoft.com/msdn). MSDN Online membership is free.
>
>Thanks again for the tip. I've read the chapters of this book that are on-line and found them very helpful. (I liked his idea of splitting business objects into two pieces so the user can have a "rich" interface.)
>
>I was wondering if and how you have dealt combo boxes in the user interface. All of this object-oriented stuff talks a lot about creating things like a "work order" object, but what if you want to give the user the ability to pick one work order # from a list? RDO creates a cursor of objects, but this seems like overkill if you just want the work order # and don't need all the work order properties and business logic. I've considered giving the work order object an object property that references an ADO recordset, then having another property that indicates which row of the recordset is the current work order.
>
>What has been your experience with this? Thanks!
>
>- Mark


I haven't worked with ADO....yet, so I can't comment.