I have two eDir trees connected with the eDir driver, and am trying to work my
way around something here that I can't quite figure out how to do.

I'm syncing the Description attribute uni-directional right now from one tree to
the other. It's uni-directional because of a feature I ran into a while ago
where a value with CR/LF in it is converted by the driver to having only LF in
it, which then syncs back the other way as a new value and ends up putting two
attribute values on the Description attribute, which is not what I want.

In Tree-1, I have lots of users with Description attributes with CR/LF in them.
Users created in this tree will have Descriptions with CR/LF in them. So, a
uni-directional sync to Tree-2 (vault) allows this not to go wrong.

But now I want to allow Description to go bi-directional, but still prevent this
from happening.

I'm starting to create users in the vault tree (Tree-2) and want the Description
to flow through to Tree-1. But I don't want to end up with two Description
values for each user object.


David Gersic dgersic_@_niu.edu

I'm tired of receiving rubbish in my mailbox, so the E-mail address is
munged to foil the junkmail bots. Humans will figure it out on their own.