The only way to avoid this is to copy the database from the old server to the new server and to install the server as an Upgrade to the "New" database
Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Misi Mladoniczky Sent: Thursday, April 12, 2012 8:47 AM To: [email protected] Subject: Re: Transferred Object "Last Changed" Value Set to Timestamp Hi, This is how it works in any version, unfortunately... Best Regards - Misi, RRR AB, http://rrr.se > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[email protected]] On Behalf Of David M. Clark > Sent: Thursday, April 12, 2012 8:24 AM > To: [email protected] > Subject: Transferred Object "Last Changed" Value Set to Timestamp > > Folks, > > My transfers from a 6.3 server to a 7.1 server via Migrator 7.1.00 p006 > set the Last Changed Time on each imported object to the time of creation > on the server. I thought this might be a problem with the Migrator "mask" > setting, but the same thing happens when definitions that have the correct > date are imported via the 7.1 Admin Tool. > > Any ideas? > > Thanks, > > -David _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
