You are here: Available Utilities > W > WIPUPDATE

WIPUPDATE

Use this utility to copy from an existing WIP database index into a new index while using the latest WIP layout.

Version 11.2 introduced a WIP layout that includes additional columns like JURISDICTN, LOCID, SUBLOCID, TRNNAME, and some others. Some of these columns are used in features introduced after version 11.2, like the stamps and signature support.

While Documaker still supports older WIP layouts, this utility lets you upgrade your WIP indexing to take advantage of newer features, without completing pending transactions.

Program names

Windows: WIPUPDATE.EXE

Syntax

WIPUPDATE

There are no parameters for this utility.

Follow these steps to use this utility:

Make sure no one is actively using the WIP database.
Create a backup directory of all the WIP files. This includes the WIP index as well as the associated DAT and POL files that contain the actual WIP transactions.
After you create the backup, delete the WIP.DBF and MDX files in the standard WIP directory, but leave the other files.

Note

The name of your WIP.DBF file may differ if you had a different name specified in the INI file.

Run the WIPUPDATE utility from the same location you run AFEMNW32.EXE. This will be the directory where the FSIUSER.INI file is located.
A window appears to ask the location of the WIP database you want to convert. Browse to the location where you made the backup of your original WIP database (and other files). Click Ok.

The update process begins and the original WIP database index is copied into a new layout for use by your workstation application. Status messages tell you how many records were found and converted.

When the update process finishes, run AFEMNW32.EXE (or your normal WIP application) and make sure you can successfully query and load WIP transactions.

Keep in mind...

The utility does not delete your existing WIP index and will report an error if you fail to remove it before running the utility. Be sure to make a backup of the original. This will serve as a fall-back in the event of failure, but more importantly is necessary for importing into the new database the utility will create.
If you try to run with an old WIP database at the destination, you will see the following message.

The destination WIP database was not created with the latest definition.

You should do one of the following

Move the original WIP.DBF and MDX to a new (backup) location and allow a new database to be created here; or

Change the File option in the WIPData control group to use a new file name.

The utility queries the destination for the key components of the source record. It does this to avoid overwriting existing WIP records. The key includes the column components for key1, Key2, KeyID, and RecType. If a match is found, a secondary check determines if the record specifies the same FormSetID. If it does, that record is not copied into the destination index because the utility assumes it is a duplicate.
When the utility finishes, you are shown how many records were found in the source and how many were copied into the destination. A discrepancy between those two numbers indicates duplications were found and skipped.