VBA - Single Sign On

Dear Kelvin,

 If your application is going to use the Explrorer like functions you note the AAMODULE_EXPLORER would good also any client customisation modules you have for explorer will also be loaded and active.

 Best Regards,

Thanks Ian,

I will give every one of the Masks a try to see if speed improves.

I don't use any customization modules in VBA but just want to be able to use some common aaApi_* functions like file/project copy, create, delete, etc.  Which Mask should I be using with safe?  Would AAMODULE_EXPLORER be suitble in this case?

Thanks again,

Kelvin

Dear Kelvin,

I think the difference is in the one time startup call to aaApi_Initialize(AAMODULE_ALL) the AAMODULE_ALL

See the SDK definition of AAMODULE_ALL

The parameter has several alternatives but the "all" parameter means customizations and modules are loaded during startup for all types (including administrator plug-ins etc) some of which are not needed to run a Projectwise Explorer like extension or stand alone application.

In short Projectwse Explorer is loading fewer modules during the one time startup then you hence faster.

 (Note during startup not during login)

Best Regards,

Ian Emery

Hi,
I use the following VBA routine to login to PW XM 8.9.4.89, whenever running
it for the very first time, it seems to have a long delay 5-10 seconds (much
longer than the time taken in double clicking datasource in PW Explorer
which happens almost instantly). Subsequent VBA runs are instant.
Any ideas? TIA, KL.

'Initialize the API
result1 = aaApi_Initialize(AAMODULE_ALL)

'Login to PW using single sign-on
result2 = aaApi_Login(AAAPIDB_UNKNOWN, datasourceName, vbNullString,
PWpassWord, vbNullString)