oh my God,,,why do i or we as a Tools user have to think about this all bugs...we just have to use it.
I never have problems yet using ADO or DAO, because i'm still a beginner to "Coding World", i am still considering some methods and will want to focus on "the best" method that i can find. I read many articles about ADO vs DAO, and all of them say that ADO is better if the BE is "Server Type" like Sql Server/MySql....so from that i decided to focus on ADO.
And please more explain about your saying "if you or your System Administrators are in complete control of the environment where your software is going to run",,,is it means that our FE should opened as Administrator Account on every computer client? (setting at : Control Panel\All Control Panel Items\User Accounts)..?
I'm using MS Access 2003, it seem that i use Microsoft ADO 2.5 Library...what bugs that i will face/have for that ADO Version.?
Regards
Hendra Agestha
--------------------------------------------
Pada Sel, 4/3/14, yahoo@craven.de <yahoo@craven.de> menulis:
Judul: [MS_AccessPros] RE: All processes based on Sql Server Stored Proc.
Kepada: MS_Access_Professionals@yahoogroups.com
Tanggal: Selasa, 4 Maret, 2014, 6:32 PM
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
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (9) |
Tidak ada komentar:
Posting Komentar