GroupWise - Import Address Book from CSV-Files


Version 1.1: After the "prototype" of my GWImp-file and due to extensive testing we found out that the 1st parameter of the CSV-file was ignored (skipped) and never imported to the NAB-file. This 4/26/05 file corrects that issue.

gwimp.vbs - 15.918 Bytes = program-file (shouldn't be changed)

gwimp.ini - 3.707 Bytes = information and parameter for program -
changeable values for your language.

Please extract BOTH files into the same directory. (the gwimp.ini-file has to be in the same directory - otherwise language is defaulted to English).

This tool uses Microsoft's Internet Explorer to present the entries of a CSV-File (filename selectable by user).

(CSV-file is a file which contains different values each separated from the other using a special character - often a "comma" therefore CSV is often read as "comma-separated-value").

Within the CSV-File the 1st line is interpreted as "headline" (and ignored for import). Other lines will be used to generate a GW-importfile after pressing <OK>-button.

The user gets an IE-Screen within which he or she can select the association to the GroupWise fields.

If one GW-Field consists of different CSV-values you may use up to 5 values (or the amount specified for "maxseq" in the INI-file) to select the proper position.

A check for overriding of import-values is done prior to the terminating execution of the script.

The results are in the same directory and with the same filename as the CSV-file and following extensions:

a ".NAB"-file containing the Groupwise-import-information

a ".STR"-file containing the previous selection.

If you run the script with the same CSV-filename more than once your previous selection of the fields will be restored from the ".STR"-file. This means that you have to make your association of the parameters within the CSV-file to the GroupWise fields only once if the CSV-file contain the same structure.

This may be confusing for the end-user, if the structure of the CSV-file changes from one call to an other but is rather useful with the same structure.
Note that if you change the association of the fields only the last selection is stored and will be retrieved from the STR-file.

You may import this file directly to GroupWise by double-click or by GroupWise-import if you previously want to create a new book first.

For other languages you may either export any addressbook (even with only 1 line) to the directory "MyDocuments" (Eigene Dateien) and change or delete the entry "ignoreNABfile" in the GWIMP.INI-file
(this works only on your computer!) or change the "defaultheader" within the INI-file as well as other
messages and information (works for everybody).

Furthermore other variables (= messages) within the INI-file should be updated to reflect your language's needs.

An example for the German language is on top of the file (and therefore overwritten by the "English" variant).

Please note, that ONLY the latest entry for a variable within the INI-file will be used (i.e.: you may have 20 lines starting with "headline", but only the last is the correct one. All previous lines may be deleted without change of the script behavior itself).

Hope you find it useful, although it uses IE and VBS...


Due to a reply from F. van der Heiden I made a further expansion /
correction to the script:

  • If you don't have XP installed the open-dialog of the file may be
    impossible to initialize. Therefore the 1st parameter will be used to
    pass the filename of the CSV-File to the script

    e.g.: "GWIMP c:\test.csv"

    indicates the file to be used. No open-dialog and therefore no error
    with W2K will appear.

  • a problem for a "subscript out of range" for the last positional
    parameter with the error in line 274 was corrected.

If any problems occur (e.g. with W2K) you have the oportunity to use a
1st parameter to specify the file-name when calling gwimp.

e.g.: GWIMP c:\test.csv


How To-Best Practice
Comment List
Related Discussions