This documentation is archived and is not being maintained.


Exchange Server 2003


This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

The atFunction interfaces were created to help Lotus Notes developers migrate applications into the Microsoft® Exchange Server 2003 environment. In particular these interfaces help developers move application logic from Notes to Exchange without redesigning existing applications, and they allow developers to add enhancements that the Exchange environment makes possible.

The atFunctions are implemented within Component Object Model (COM) interfaces in a library called MXAT.dll. This DLL must be installed on the computer where any script or program using the atFunctions will be run.

Although all original @functions from Lotus Notes are addressed in this document, only the ones that make sense in the Exchange application environment are implemented within MXAT.dll. The Lotus Notes application environment is different from that of Exchange in many ways. For example, the @DBLookup function for Notes databases is not implemented in MXAT.dll because in the Exchange environment data is stored in data storage systems other than Lotus Notes. Another example is the @Platform function, which on a Notes installation returns the version of Notes under which the script is running. This functionality would make no sense in the environment of Exchange.

You can use the atFunction interfaces not only for migration, but also to provide general functionality for working with objects in the Exchange store. Anything you can access through COM is suited for use with the atFunction interfaces. You can use the atFunction interfaces with any programming language that supports COM, such as Microsoft Visual Basic®, Visual Basic Scripting Edition (VBScript), Microsoft Visual C++®, Microsoft JScript®, and C#.