vbaproject.otm

[Darrin]

Hello,

I am pretty fresh at development in the Outlook/Exchange environment.

Using:
Windows2000
Exchange 5.5
Outlook2000
SQL 7.0

I am looking at creating some public forms that interact with the SQL
database.
Adding, deleting, modifying records.

I started playing around with forms on a machine with SQL but without
running exchange. When writing the VBA script to attach to the database it
appears that it is being saved in the "vbaproject.otm" file.

Question:
In writing this script will I have to distribute the "vbaproject.otm" file
to every user or is there
a way to reference everyone to the same vbaproject.otm file?
I would rather not have to distribute a new vbaproject.otm file each time a
change was made
to the script.

Any suggestions or ideas on making this process easier would be greatly
appreciated.

Thanks!!

-Darrin

[Neo [MVP Outlook]]

To clarify...

If you are creating a form and the code is behind the form, then the code is
not saved in vbaproject.otm. The only thing saved in vbaproject.otm is vba
macros.

Example 1:
* Open Outlook and press ALT + F11
* This is the VBAProject.OTM area where you create VBA Macros.

If this is where your code is stored, then yes -- you would have to deploy
this file to all users or wrap the code into a COM AddIn and deploy that.
FWIW, the COM AddIn is the way to go in this case.)

Example 2:
* Open Outlook
* Create new message
* Select Tools | Forms | Design This Form
* Select Macro button
* This code is stored with the form in question.

Code will be saved with the form. Best choice to deploy form is the
Organization Forms library because when you update the form with a newer
version, users will pick up the changes the next time they open the form.

"Darrin" <dbro...@versatilesi.com> wrote in message
news:ORQkGOOqAHA.1412@tkmsftngp03...

[Hollis D. Paul]

Neo [MVP Outlook] wrote:
> Best choice to deploy form is the
> Organization Forms library because when you update the form with a >
newer version, users will pick up the changes the next time they open >
the form.
>

The down side of this is that you have to have the version number in
the form name, or your users will continue to use the forms cache and
will come crying for help about why they aren't getting the new form.
You have to educate them to pick the latest form name.

Hollis D. Paul [MVP - Outlook]
Hol...@outlookbythesound.com
h...@compuserve.com
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195

Mukilteo, WA USA

[Darrin]

Thanks for your assistance!!!

-Darrin

"Hollis D. Paul" <Hol...@outlookbythesound.com> wrote in message
news:VA.00000a6b.538ed409@obts-outlookdev...

[Darrin]

Thanks for your assistance!!!

-Darrin

"Neo [MVP Outlook]" <n...@mvps.org> wrote in message
news:#qVwWiRqAHA.1840@tkmsftngp03...