Ernie,[color=blue]
> - Since I have to go thru a central purchasing department
> to obtain software, I'm not sure that we will be able
> to obtain VB 6.0.[/color]
Seeing as you have a license for VB.NET, you have a license to VB6.
http://msdn.microsoft.com/vbasic/pre...downgrade.aspx
It may cost you a small fee ($20 US) for media.
[color=blue]
> that did look like the best solution for us at this particular point.[/color]
?? Its easier to write a COM add-in in VB6 for Outlook, then it is in
VB.NET, however both are doable. With Outlook 2000, you have a greater
chance of getting the Security prompt from your application. Which can be
addressed by the links I gave earlier or Redemption. For information on
Redemption see the regular Outlook development groups...
Hope this helps
Jay
"Ernie" <anonymous@discussions.microsoft.com> wrote in message
news:CA29D169-DCED-46D3-9972-206792467C62@microsoft.com...[color=blue]
> Thanks for the various replies; some additional information:
> - this is an in-house application; it will not be sold
> - we will be using Outlook 2000 for the near future; migration to a newer[/color]
version of MS-Office is some time in the future. Probably tied into the
purchase of new computer systems. Any support of multiple versions will be
limited to the conversion / installation period. However we don't
anticipate much support being required since we probably won't be accepting
very much in the way of change requests (yeah, famous last words!)[color=blue]
> - Since I have to go thru a central purchasing department to obtain[/color]
software, I'm not sure that we will be able to obtain VB 6.0. I will check
into that, though - that did look like the best solution for us at this
particular point.[color=blue]
>
> Thanks,
> Ernie
>
> ----- Jay B. Harlow [MVP - Outlook] wrote: -----
>
> Ernie,
> Are you staying with Outlook 2000 or can you upgrade to Outlook 2003?
>
> Is this an in house app or do you sell it? (do you need to support[/color]
multiple[color=blue]
> versions of Outlook).
>
> I would consider creating a properly constructed COM Add-In in VB.NET[/color]
that[color=blue]
> uses the PIA for Outlook 2003. As an Outlook 2003 Add-In will avoid[/color]
the[color=blue]
> security prompt.
>
> For a list of articles on using Outlook from .NET see:
>
>
http://www.microeye.com/resources/res_outlookvsnet.htm
>
> For a plethora of automating Outlook with VBA, VB6, and VBScript see:
>
http://www.outlookcode.com/
>
> To avoid the Outlook security prompts its generally easiest to create[/color]
a[color=blue]
> properly constructed COM-Addin for Outlook 2003. There are other[/color]
methods[color=blue]
> available for other versions of Outlook...
>
> See:
>[/color]
http://msdn.microsoft.com/library/de...scomaddins.asp[color=blue]
>
> Further info can be found at:
>
http://www.slipstick.com/dev/ol2003problems.htm
>
http://www.slipstick.com/outlook/esecup/admin.htm
>
> The links I gave have samples of creating add-ins.
>
> Both of these are good articles to start with:
>[/color]
http://msdn.microsoft.com/library/de...addinvbnet.asp[color=blue]
>
>
http://support.microsoft.com/?kbid=302896
>
> Also, be certain you have explicitly installed the Outlook PIAs!
>
> Hope this helps
> Jay
>
>
> "Ernie" <anonymous@discussions.microsoft.com> wrote in message
> news:9C57E010-AFF3-4E6A-9B64-567B155C457B@microsoft.com...[color=green]
> > We have an Outlook 2000 VBA application - 8 user forms, and about a[/color]
> thousand lines of code - that we wish to distribute. We know that we[/color]
can[color=blue]
> password-protect the code, but that does not give us the desired[/color]
level of[color=blue]
> security.[color=green][color=darkred]
> >> We plan to use VB.NET to create an executable file which we will[/color][/color]
> distribute to our users. We have tested this, and it works.[/color]
However, I've[color=blue]
> seen some references on various newsgroups indicating that this will[/color]
not[color=blue]
> work, and we need to use Visual Studio .NET instead. We do not have[/color]
a copy[color=blue]
> of Visual Studio .NET; it's expensive and we'd rather not purchase it[/color]
if we[color=blue]
> don't need it. Can someone clarifiy whether we do or do not need it?[color=green][color=darkred]
> >> Thanks,[/color]
> > Ernie[/color]
>
>
>[/color]
