Reindex (Pre-Archive) Script Hook Not saving Keywords?

[Christopher_Per]

Good Morning - 

Recently I have upgraded my Test System from 13.2 to 15.2. One of the things I tested deal with a special VB Script I have running in the background. Basically, if a Keyword is of a certain value, I pop up a message stating that other keywords need to be filled and prevent the user from continuing. What I noticed though is that under the Reindex(Pre Archive) script hook, Onbase automatically reverts to the original keyword values. So if I reindex the document, make some changes to the keywords and forget something, the script will kick in and revert back to the original values of the document instead of keeping the current values. 

Keep in mind that this script works completely fine in 13.2, and when i try to reindex something and I get the message that i need something, the new values are retained. 

So my question is this: has anything changed in this area from 13 to 15? If so, is there a way around it? Anything you can provide would be greatly appreciated. Thank you. 

[Scott_McLean]

Does your script call the Core API (DMCoreX)? If so, you'll need to rework the script, since that API has been removed in v15. If you call the OnBase Client API via the ScriptAPI object, you might need to redo the DCOM configuration or register the DLL following the new installation.

[Christopher_Per]

Hi Scott -

I don't think I am using any of the Core API. All of my code resides in Sub Main 35 (which I believe is the non core part of the code). Also, I am using the Automation Library only. I am not using the thick client (with functions that start with mz...)

If I need to register DLLS, which ones should I be registering?

[Patrick_Sweeney]

Hi Chris,
Scott is correct in that the biggest thing to change between 13 and 15 was the removal of DMCoreX. The dlls that he is likely referring to are mzapi.dll and mzasp.dll.

Is there more detail you can provide about how you're evaluating the document keywords and how you're cancelling the reindex process? It might help in identifying exactly what changed and why you're seeing different behavior. Thanks,

[Christopher_Per]

Hi Patrick -

The way I am handling this is I have a library in the background. This library has flags that turn on based on certain keywords and their values. If no message is needed, then the return code I am using is 0. If I do get a message, I am returning a code of -1.

Perhaps I need a different return code?