I am currently embarking on a database project in which I will need to set a
great many security permissions through VBA code, and am faced with the
choice of DAO or ADO.

My understanding is that ADO is the future, and it is generally better to
use ADO than DAO. However, the Mirosoft Access Security FAQ document at

http://support.microsoft.com/support...ent/secfaq.asp

says that ADO falls far short of DAO when it comes to security, and that it
is better to stick with DAO.

On the other hand, another document on the Microsoft website

http://msdn.microsoft.com/library/en...ate_topic7.asp

goes and tells you all the ADO code you need for securing databases, so
whoever wrote that article obviously thinks it works.

Which one should I believe?

Many thanks



--
Adam

(remove 'nospam.' from email address to reply)

ADO (actually, ADOX) has some shortcomings regarding security. See the MS
Security FAQ (specifically question #45) for info:

http://support.microsoft.com/default...#_Toc493299714

"Adam" <(E-Mail Removed)> wrote in message
news:z9_4b.1097$(E-Mail Removed)...
> I am currently embarking on a database project in which I will need to set
a
> great many security permissions through VBA code, and am faced with the
> choice of DAO or ADO.
>
> My understanding is that ADO is the future, and it is generally better to
> use ADO than DAO. However, the Mirosoft Access Security FAQ document at
>
> http://support.microsoft.com/support...ent/secfaq.asp
>
> says that ADO falls far short of DAO when it comes to security, and that
it
> is better to stick with DAO.
>
> On the other hand, another document on the Microsoft website
>
>
http://msdn.microsoft.com/library/en...ate_topic7.asp
>
> goes and tells you all the ADO code you need for securing databases, so
> whoever wrote that article obviously thinks it works.
>
> Which one should I believe?
>
> Many thanks
>
>
>
> --
> Adam
>
> (remove 'nospam.' from email address to reply)
>
>