![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| ||||
| ||||
|
|
"Bob Barrows" <reb01501 (AT) NOSPAMyahoo (DOT) com> wrote in news:iaabbj$br1$1 (AT) news (DOT) eternal-september.org: Composer wrote: What do you mean, ADO is dead? I guess I have to slightly disagree with David. ADO of course is as dead as DAO. DAO is *not* dead -- it is in continual development in tandem with the Jet/ACE database engine. |
|
ADO.Net is the new paradigm. Additionally, DAO is single-threaded, so if your application is multi-threaded (such as a web application), you need to use ADO. Web applications should not be using a Jet/ACE datastore, precisely because of this issue. |
|
In the present case, the issue was not even ADO but JRO, and JRO was being recommended to do something that DAO can already |
|
The number of things ADO can do with Jet/ACE that DAO can't is actually pretty small. Of those things, very, very few of them are essential or even very useful. |
#12
| |||
| |||
|
|
David-W-Fenton wrote: "Bob Barrows" <reb01501 (AT) NOSPAMyahoo (DOT) com> wrote in news:iaabbj$br1$1 (AT) news (DOT) eternal-september.org: ADO.Net is the new paradigm. Additionally, DAO is single-threaded, so if your application is multi-threaded (such as a web application), you need to use ADO. Web applications should not be using a Jet/ACE datastore, precisely because of this issue. Not even small-scale intranet applications such as are used in many locations? Please, get off the high horse. The advantages of using asp instead of fat clients that don't need to be installed everwhere they are used are very appealing to IT depts such as the one I work for. |
|
In the present case, the issue was not even ADO but JRO, and JRO was being recommended to do something that DAO can already So? The OP was looking for an ADO solution. Jeez! |
|
The number of things ADO can do with Jet/ACE that DAO can't is actually pretty small. Of those things, very, very few of them are essential or even very useful. So? The fact that some developers do find them useful is irrelevant? I think not. |
#13
| |||
| |||
|
|
And batch updates were never a possibility for my app. *One user presses one button and I have to react to it. On Oct 28, 9:11 pm, "David-W-Fenton" <NoEm... (AT) SeeSignature (DOT) invalid |
|
I really don't know what the hell you're talking about. You replied to one of my posts from over a month ago and are bringing up issues not addressed in my post. So I really don't have a clue what the hell you're talking about with this SEEK tangent. |
#14
| |||
| |||
|
|
Composer wrote: And batch updates were never a possibility for my app. *One user presses one button and I have to react to it. On Oct 28, 9:11 pm, "David-W-Fenton" NoEm... (AT) SeeSignature (DOT) invalid> wrote: I really don't know what the hell you're talking about. You replied to one of my posts from over a month ago and are bringing up issues not addressed in my post. So I really don't have a clue what the hell you're talking about with this SEEK tangent. Um, pardon me, David, but please read your post of 25 September 8:14pm, where you recommended that I "convert the sequential process into a set-based process that uses a single SQL UPDATE statement to make all the changes in a batch". |
|
You may know a lot more about this technology than I know, but you waste a lot of your energy dissing people for no good reason. |
![]() |
| Thread Tools | |
| Display Modes | |
| |