![]() | |
#11
| |||
| |||
|
|
On Thu, 25 Nov 2010 16:41:55 -0800 (PST), TechVsLife techvslife (AT) gmail (DOT) com> wrote: No, they're not using disconnected recordsets. * I think it was that you could call a stored procedure and get a recordset returned. * But DAO also fully supports returning recordsets from stored procedures. Ah, I stand corrected. I doubt that was why then. |
#12
| |||
| |||
|
|
No, they're not using disconnected recordsets. * I think it was that you could call a stored procedure and get a recordset returned. * But DAO also fully supports returning recordsets from stored procedures. Ah, I stand corrected. I doubt that was why then. Is it perhaps that with ADO, you can get an editable recordset? And bind it to a form? |
#13
| |||
| |||
|
|
Is it perhaps that with ADO, you can get an editable recordset? And bind it to a form? Yes, he is using ADO in that fashion. |
#14
| |||
| |||
|
|
Is it perhaps that with ADO, you can get an editable recordset? And bind it to a form? Yes, he is using ADO in that fashion. Not sure what the advantage of ADO over DAO is, which can also bind editable recordsets. |
|
Is is that ADO can get editable recordsets from certain types of stored procedures and table functions, and DAO cannot, or something else. (since DAO can bind editable sql server tables via linking, and local queries on them, and call stored procedures or pass through sql for write & other operations) Too bad DAO won't get further enhancements to support sql server; |
|
but ADO is also dead. (The windows development world is in a more confused terrain than usual after winforms (wpf? silverlight? asp? javscript/ html5?).) |
#15
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |