Take a look and see if you can add pers_companyId to the screen.

Or, you can do this in the database, the link is on the pers_companyId. If you do this though, make sure you do the same for all linked records to that person.

There is a component called Clone Person (in the partner site) which may also help if you are not happy to change the ID's in SQL. Just search Clone Person. I haven't used them my self so you may want to test first.

I think it will run through and change all related records.

just did a quick test and adding the pers_companyid to the person screen does move the Opportunities , communications, address and notes across to the new company when you select a new company but if you have different territories between the companies then these are not changed. I wouldn't want to do this for Sage 200 CRM as I would imagine the foreign ID's would cause problems. I would test thoroughly and check all the SQL tables linked to the person. I'm not sure what it would do if you also had custom tables linked to the person either.

Not sure as well what Sage would say about this method of moving people, but still a nice call from Toby.

I don't have any issues changing it on the back end what we are looking to do is to allow the end users to be able to make this change and it update all the communications and other entities that are tied to the person from the UI not on the back end. Wasn't sure if there was something there in the system I have over looked for if this just isn't possible. I know we could add the company field and it would allow this to be changed but correct me if I am wrong but it will not update the communications, case, or any other entities attached to a person.

Thanks Toby and Chris for the quick replies

Yeah, if it is an integrated system, don't move the people, it is more than likely to cause a world of pain.

You could of course look at writing a function yourself to move a person. Have a stored proc assigned to a button, that goes through all the tables and updated the companyId where needed.

We created something like this, an "Unlink" checkbox on the Person summary. A trigger updates the associated records, then resets the checkbox.