Andrew
I remember that ADO snafu. The work-around was to use late-binding for ADO objects.
-Bill Mosca
---In MS_Access_Professionals@yahoogroups.com, <yahoo@craven.de> wrote :
---In MS_Access_Professionals@yahoogroups.com, <yahoo@craven.de> wrote :
You're welcome Hendra,
I am going to stick my neck out a little though and say that if you can avoid ADO you might avoid some pitfalls. Before I rant-off, if you or your System Administrators are in complete control of the environment where your software is going to run you shouldn't have any problem with ADO so the following might needlessly worry (and can be ignored...)
Up until now I have never had a problem with DAO but I've had several problems with ADO (using VB6, Access and Excel), the worst one of all was when Microsoft *broke* 32-bit ADO while trying to fix a 64-bit security issue. It took them ages to fix it. Then, which version of ADO are you going to reference and use? If you are lucky or control the client computers you'll be able to rely on a particular version being available but even then I get funny feelings when I see the filenames used, for ADO 2.0 through to 2.8 the DLL is called msado20 through msado28 so guess what the 6.1 Version ADO DLL is called, that's right msado15 HUH? I'm sure they had a good reason for doing that, just like they had a good reason for breaking ADO 2.8 (in the name of security) but it raises (probably unfounded) doubts in my mind.
Yours, Andrew
I am going to stick my neck out a little though and say that if you can avoid ADO you might avoid some pitfalls. Before I rant-off, if you or your System Administrators are in complete control of the environment where your software is going to run you shouldn't have any problem with ADO so the following might needlessly worry (and can be ignored...)
Up until now I have never had a problem with DAO but I've had several problems with ADO (using VB6, Access and Excel), the worst one of all was when Microsoft *broke* 32-bit ADO while trying to fix a 64-bit security issue. It took them ages to fix it. Then, which version of ADO are you going to reference and use? If you are lucky or control the client computers you'll be able to rely on a particular version being available but even then I get funny feelings when I see the filenames used, for ADO 2.0 through to 2.8 the DLL is called msado20 through msado28 so guess what the 6.1 Version ADO DLL is called, that's right msado15 HUH? I'm sure they had a good reason for doing that, just like they had a good reason for breaking ADO 2.8 (in the name of security) but it raises (probably unfounded) doubts in my mind.
Yours, Andrew
__._,_.___
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (8) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar