Running list of version translation problems for example ver 19.3 to 16.1

I have not seen anything that has been lost. The only way anything can really be lost is if there is an entirely new field created by oracel in P6 version 19.3 that is not in version 16.1 

Also what do you think happens when you are in verions 19.3 and select export xer file you have the option to export all the backwackwards to version 5.0

Activity id the same

duration the same 

remaining duration the same

constraints the same

calendars the same

different types of predcessors and succuessors the same

lags the same

activity codes the same

expenses the same

resources the same

forward and backward pass the same

activity types the same

Thanks, you are the best.  Just making sure there was not something I didn't realize.  Oracle needs to use a standard because there are now so many versions everyone has to adjust it most the time, and most folks don't know you can do it yourself.