Information générale
Catégorie:
Programmation Orientée Object
That's what I thought. Is there any particular reason you prefer ADO?
Thanks
Kev
>You can't use views in an n-tier application. Data access will be passed as either XML or ADO (which I prefer).
>
>
>>Thanks for the response.
>>
>>Can you pass views in VFP though?
>>
>>Thanks
>>Kev
>>
>>>What if you have a customer and their orders on the same form? What would thisform.odata.getvalue('CustID') return? Would it return customer.custid or orders.custid?
>>>
>>>My point is that I don't think having one oData instance on your form is going to get you very far, and you are going to do a lot of work doing your own data binding. Basically, Microsoft's controls work very well binding themselves to tables, views, and cursors. All of the Microsoft RAD tools push you in the direction of having your middle tier return views that your UI can bind to.
>>>
>>>So, to answer you question, the UI would simple bind to a view or REPLACE in a view. Your business object would be responsible for tableupdating the view.
>>>
>>>>Hi
>>>>
>>>>What is the best way to retrieve/save values from a record in a table in n-tier design?
>>>>
>>>>I was thinking something like a thisForm.oData.GetValue(cField) to retrieve the value, and a SetValue(cField) in the Valid of the textbox or something.
>>>>
>>>>Any suggestions?
>>>>
>>>>Thanks
>>>>Kev
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement