index
Posted: Fri Jun 12, 2020 9:00 pm
That’s no big problem… I could give you a connection handle and a cursor if it were only that. But there is no provision for that. If it were only that trivial I would think they could’ve made it work. Perhaps X# can.
My point is I can think of many cases where one might create a local cursor that does not come from an initial SqlExec() statement but then want to update a SQL Server table from it. If I could give you a connection handle to go with that cursor, along with all the other required CursorSetProp() settings, it should be able to make it work. But it doesn’t provide for that, and I see no reason why it couldn’t. Do you see my point?
My point is I can think of many cases where one might create a local cursor that does not come from an initial SqlExec() statement but then want to update a SQL Server table from it. If I could give you a connection handle to go with that cursor, along with all the other required CursorSetProp() settings, it should be able to make it work. But it doesn’t provide for that, and I see no reason why it couldn’t. Do you see my point?