AccessWPS Change History

AccessWPS CHANGE HISTORY


 * V1.0a

The items fixed in Version 1.0a are:

1. The AcsTest program has been included in the package. Both the EXE file and the source are included. The EXE will verify that AccessWPS has been installed correctly, will identify the version number of both the ACCSSWPS.DLL and the ACSAGENT.DLL and will dispaly a dump of all the AccessWPS variables. The source code shows an example of how the AccessWPS Agent object can be created.

2. A version number along with a way to get it returned, has been added to the code. See the discussion of AcsVersion in the AccssWPS.TXT file. The version information will be returned as part of the output from the AcsTest program.

3. Additional text has been added to the discussion on pointers and memory allocation. The purposeof the additional text is to alert developers that they have to be careful with certain types, especially the SOM types, to be sure that they handle the types that are actually pointers correctly. Specifically, the somId type is discussed.

4. Because of the addition of AcsTest, a dynamically linked DLL, Acsapidl.dll, has been added to the package. It is intended that both the AcsAgent.dll and Accsswps.dll files will use this CSet/2 API DLL in a future release. There were problems getting the Agent Class to register correctly and the AcsAgent Object created. Therefore, I eliminated all of the differences between my procedures and the ones in the code that I used as the starting point. One of the differences was static linking versus dynamic linking, which I hope to remove.

5. Additional text has been added in the installation area because of the additional DLL and the AcsTest program.

6. A new section has been added to the documentation file and it discusses the kinds of things that might be necessary if there are problems creating the AcsAgent Class and or Object, thus leaving partial information in the INI files. This section is entitled, Recovery.

7. There were a number of problems with the Registration of the AcsAgent Class, the creation of the Object, the creation of the necessary control semaphores and the removal of all of these items when any one of a number of errors were encountered. Certain erros can leave some of the information in the INI files and can even leave Objects and/or Class information active in the WPS Process. A number of changes have been made to the initialization and termination routines in an attempt to resolve these problems. I am not sure that every condition will be handled. If there is a question about something, then you can use the AcsTest program to verify whether things are working or not. If the AcsTest program does not clear things up...but running it a couple of times...then the items listed in the recovery section of the documentation should be tried. If these do not work, then you should call Carry Associates.