AS a "user" you don't normally have to think about these things. As a developer however, you *might* and as a developer selling solutions onto machines you have no control over, you *have* to. I sometimes like to think of these problems as Microsofts way of keeping us developers in a job :D
ADO has one advantage over DAO, you can run "asynhronous" requests meaning you can ask the SQL Server to do something and while it is doing it, your program can do something else on the user's machine (if there's nothing better to do then I have an animated "Please Wait" and a time-taken display.... much better than just the wait cursor.)
You might like to consult this link
http://msdn.microsoft.com/en-us/library/windows/desktop/ms676506%28v=vs.85%29.aspx
to learn about the Versions of ADO and where you might find them already installed.
Ot the informative Wikipedia article (check to see if it's available in your prefered language:
http://en.wikipedia.org/wiki/Microsoft_Data_Access_Components
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (10) |
Tidak ada komentar:
Posting Komentar