Thick Client 4 entry points questions

[Terry_Vantreese]

Hi,

I see that ScriptAPI.Object is accessed using VBScript Automation. 1. Is that right? Are there other situations to use this?

2. In what situation is "Client.MZAPI" accessed? (Through Visual Studio C#/VB.NET Projects?)

3. In what situation is "OnBaseScriptObjects.OnBaseScriptObjecs.1" used? And it appears to use mzASP.dll in same situation. Is that right?

4. In what situation is "OnBase.OBAPI" used?

5. When is MZAPI.dll used? In one of the 4 above? Or other situation?

[Ryan_Wilson1]

1) Yes, that is the only case you would use ScriptAPI.Object

2/4) Client.MZAPI and OnBase.OBAPI can both be used through C#/VB.net projects, and they both expose the same functionality.  The difference is in where they are implemented - Client.MZAPI is implemented in the obClnt32.exe executable, whereas OnBase.OBAPI is implemented in mzAPI.dll.  As stated in the SDK, the recommendation is to use Client.MZAPI because OnBase.OBAPI is considered legacy.  Usually the only reason to use OnBase.OBAPI would be if you were using DCOM to connect to obclnt32.exe running on another machine on your network.

3) OnBaseScriptObjects is used when writing VBscripts that will be executed from outside OnBase (thus not through the Automation API). This has the same functionality as Client.MZAPI.

See the "OnBase Client API Interfaces" page in the SDK for this information.