Hi Bruce: If you don't want to flatten or normalize you U2 files you can use JSON format. It is an open standard for languages like Java, JavaScript, jQuery, Ruby, Python, PowerShell, C#, and PHP to name just a few.
When we looking at transferring data between sites, programs and the WEB, JSON was much easier to understand in Java because it maps into Java Objects directly. Here is a sample of a file read using JSON: [{"IdCode":"32828","TypeCode":"14","Length":"28'","Cubes":"720","MfgDate":"0 3/01/2009", "VehicleNo":"","Year":"2005","LicenseNo":"","MfgCode":"AJ","AssignedTerminal ":"0", "Permits":["DIA"],["FCA"]],"XLr8Company":"01","XLr8NewItem":"0","XLr8CheckSu m":"62138"}] If you equated this to a variable oData, the IdCode field would be oData.IdCode. The multivalve field Permits would be referenced by oData.Permits[0] and oData.Permits[1]. Then your data transmissions would match an industry standard. Regards, Doug www.u2logic.com "U2WebLink(tm) for Java" _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users