Distributing a VBA project

[hals_left]

Hi,

I have a few questions on deploying a vba project to distributed users.


thanks.

How can I allow macros and vba to be trusted for certain templates and
documents I distribute, so that the enable macro dialog doesnt appear,
but not have to allow all macros.

How can I programatically set a reference to ADO versions
2.5,2.6,2.7,2.8 depending on what is installed on the client.

How can I have a single file with database connection and
authentication details , shared by many documents and templates, so
thast if the IP of the daatbase server changes I only have to update
one file and not a whole set of templates.

 

[Jezebel]

How can I allow macros and vba to be trusted for certain templates and
documents I distribute, so that the enable macro dialog doesnt appear,
but not have to allow all macros.

You can't. It's up to the user whether or not to permit your code to run.
The best you can do is digitally sign your code with a third-party
certificate.

How can I programatically set a reference to ADO versions
2.5,2.6,2.7,2.8 depending on what is installed on the client.

Use late binding instead.

How can I have a single file with database connection and
authentication details , shared by many documents and templates, so
thast if the IP of the daatbase server changes I only have to update
one file and not a whole set of templates.

Create a file with the details you need, and read it.