Showing Columns in Shared Address Books
Novell Cool Solutions: Trench
By John Burns III
|
Digg This -
Slashdot This
Posted: 21 Feb 2001 |
Current Version: GroupWise 5.5 EP
I have been struggling with the problem of not all columns showing up when viewing an address book that was shared with me.
Via a little "reverse engineering" of the Registry settings for the specific address book that I was interested in, I found the "Keys" associated to it, figured out which ones related to the columns I wanted, and then switched the "Show=" string value to "Yes" for the ones I wanted to see, and "No" for those I did not.
Additionally, I was able to set the "Primary Sort Key" to the correct column, and reset the column order using the Position value.
I have not had any ill effect on the other five address books that I use, nor does revoking the share and then resharing it cause any ill effects. The Registry keys are not removed when the Share is revoked, making it available if it is reshared, with the identical name most likely. I did not test renaming the share, but it seems logical to me that it would not match if it was not identical, therefore generating new keys in the Registry. The columns showing up in each book still show up. I have added or removed columns in the other books without seeing a change in the others (including the book shared to me).
Important Note: These changes make the shared address book much more useful to me. Bear in mind that it is always risky when you root around in the registry, and you should not try this unless you are absolutely confident you know what you're doing in there.
Here is the "Field Cross-Ref" list that I "generated" by turning all values to "no", and then on one at a time to see their effect.
|
Ending key value |
Field Name |
|
3001001 |
name |
|
3A08001 |
office phone number |
|
3A18001 |
department |
|
3A23001 |
fax phone number |
|
3003001 |
email address |
|
3A06001 |
first name |
|
3A11001 |
last name |
|
3A17001 |
title |
|
3A29001 |
address |
|
3A27001 |
city |
|
3A28001 |
state |
|
3A26001 |
country |
|
3A2A001 |
zip code |
|
3002001 |
email type |
|
3A19001 |
mail stop |
|
3A09001 |
home phone number |
|
3A1C001 |
cell phone number |
|
3A1A001 |
phone number |
|
600B001 |
greeting |
|
600F001 |
owner |
|
3A16001 |
organization |
|
3004001 |
comments |
|
6604001 |
domain |
|
6609001 |
additional routing |
|
6605001 |
post office |
|
6603001 |
guid |
|
6607001 |
nds distinguished name |
|
6608001 |
network id |
|
3A00001 |
user id |
|
660D001 |
internet domain |
|
8000001 |
network id |
|
8002001 |
user defined 1 |
|
8003001 |
user defined 2 |
|
8004001 |
user defined 3 |
|
8005001 |
user defined 5 |
|
8006001 |
user defined 6 |
|
8001001 |
no field |
|
8007001 |
user defined 7 |
|
8008001 |
user defined 9 |
|
3A21001 |
no field |
FYI
- Because the above key values all end with the letter 'E', I left it off (just in case you were wondering).
- I also do not show the entire path, because the path would be different for each address book. Showing the path for mine would be useless to others.
- Because this address book will be shared with about 40 other staff, we will export the associated Registry keys for this book to a ".reg" file so that the other staff do not have to wander the Registry to make the changes.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com