Hello Sebastian,

Thank you for your additional responses.

Yes, it is good news that the few fields that I need to duplicate are at least stored in one column as traditional columns.  It will make it neater to duplicate.

Just to re-iterate my intentions:

1) All usernames and passwords will be handled by DNN Exclusively

2) User Creation will be handled by DNN Exclusively

3) On Creation of a user, I will execute and sql to insert a base Person in my people table.  All I will have populated at that point will be the following columns
PersonId, FirstName, Surname, DNNUserId.  The execution of this sql is one time only.  No chain of events to worry about here.

4) I may create a trigger to update the users table which will do as follows "Set Users.FirstName People.FirstName, Users.LastName = People.LastName where People.UserId = Users.UserId"
This is one directional syncing and I hope it will be easy to maintain.

The downside with this solution is that if the user goes to their profile and makes a change, they will loose it next time they change their People.*Name details.


My instinct at this point is that it is not a big issue, but I can try to improve it later by making the syncing bi-directional.

Can you think of any other easy, simple way I can implement bi-directional syncing?  I worry about triggers firing indefinitely.  Users Triggers People, People Triggers Uers, Users Triggers People again etc

Thanks Sebastian

Mark

---

Mark Breen Ireland 1987 BMW R80 g/s

Hello Sebastian, I have implemented the two triggers and in the development system they seem to be working perfectly. I am going to buy Data Springs full collection today and use that to create the rest of the registration and log in functionality. Thanks for your hints and when I finalise the triggers, I will post them back here, hopefully for someone elses use again.

---

Mark Breen Ireland 1987 BMW R80 g/s