Let's just suppose that a site had developers working in RPG and in 2e, and suppose the RPG developers were not good at database architecture or coherence, or disciplined about nomenclature, or anything we take for granted (or that I used to rampage about when we I used bare knuckle RPG) Now, someone comes on the scene who starts with database design and integrity as guidelines, and only later needs to worry about code and functionality, (because 2e does all that stuff, given a database design that works.)Files get assimilated, linkages to RPG get built, generated functions get SCNSRC run over them to make inconsistent interfaces callable. In short, some better stuff gets built, and functions for testing and diagnostics get built along the way because, well, because that's the way good systems get put together. Finally we get to a point where files can't be assimilated to the main model, because there are just too many colliding field names and inconsistent data typing and so on. Some functionality, initially intended as developer only utilities, gets built over peripheral files which are in a separate model. 2 models - the main production one, and a second, 'developers toolkit' It turns out that the functionality provided in the toolkit is a Good Thing and we'd like it to be available on the production machine for diagnostics, and even (with some additional user security) make some of its finer points available to the general user community. - is anyone still awake? - here comes the question. . Astounding new features(!) such as RTVCND names work by bringing data from the xxVLLSP file, using surrogate number as key. To what extent is it possible to combine the content of the two files to a common run time file? the surrogate numbers differ. Is there a way of synchronising surrogate number allocation in the same way as field names (and of reallocating the duplicated existing ones?) I'm assuming that creating a third model, and exporting from each model into the new one, would synchronise everything, but because the two data models are incompatible, I can't do this. The option of regeneration of existing files into production is not possible, as too much functionality is in ill documented RPG. Message allocation is just about OK, and a few checks and changes to some early messages will allow message files to be combined, but I'm at a loss as to how to get conditions values files to marry up. all suggestions gratefully received..