-
administrator features
hello,
i'm printing and replying an email from outlook with vba coding!
it was working fine on mine with Office2K but the
#$#@ client got XP even though we said 2K!
and the problem come when it receive email, the client is prompt
when i access the address book or when i use myOlkObj.Send
here's some info on how to avoid it, but i'm not familiar
with the administrator features!
here's, that from the link below
Code:
As a developer, you have various options when you try to avoid the security features. To summarize your typical options depending on where you are developing your solution:
Outlook custom forms : Publish forms so that they are not one-off forms, or use the administrator features to enable VBScript code in one-off forms to run.
Outlook Visual Basic for Applications : Use the administrator features to disable object model restrictions, or convert your Visual Basic for Applications code to a COM Add-in, and then register it by using the administrator form.
COM add-ins : COM add-ins can be trusted if an administrator registers them by using the administrator form. However, when you are using a COM add-in, only the Outlook object model is exempted; the CDO object model will still generate warnings.
Automating the Outlook or CDO object models : Use the administrator features to disable object model restrictions.
If feasible, you may want to consider redesigning your solution so that it runs on a server instead of a client. Server-based APIs are not protected by these e-mail security features.
btw, the problem is with Outlook 2002 on Win98