Ok, I am attempting to clarify the required use of the RESIZE command, when you have a UNIVERSE or a UNIDATA DB attached to Cache. Traditional UNIVERSE / UNIDATA databases 'require' that hashed files be re-sized according to historic use, to prevent file overflow (aka. performance issues). It is not clear if that requirement is fully eliminated by attaching one of these databases to Cache. It is clear that, if you do not allocate 'enough' space on Cache for the database 'as a whole', that is a problem.

0 6
0 72

I am creating a new HL7 DTL item. I put the from as HL7 and the to as XML, hence, those Ens classes were loaded into the new DTL. However, on the map screen, both the left and the right column only show 'source' and 'target', and no other fields. I pictured that when I included these classes, both columns would pull the corresponding 'schema' to show all the to/from fields, but, they did not. Is that right?

0 2
0 57