Good Morning All:
We currently have a couple of database drivers and I am trying to get a
good understanding on how a triggerless driver detects a change to push
this information over to eDirectory. Does a triggerless driver compare
"state" information (Database snapshot) to eDirectory or to a previous
"state" information. Currently, we are experiencing out of sync
attributes on users, its set one way in the database and then a
different value on the user in eDirectory. I have read all the
information I could get my hands on, some of the changes on these users
were made over a year ago, so I don't have the log files to go back to
find out if there was a problem. I am getting questioned by the
"uppers" if it does a compare from the database to eDirectory why is it
out of sync, for that question I don't have a good answer.

If anyone could provide me with any incite on how this works I would
greatly appreciate it. Somehow I am missing the boat on this.

Thank you very much for your help in advance

Driver_Girl's Profile:
View this thread: