This article is an e-mail sent to the uniface newsgroup by Arthur Barrett and included here because we think that it is a very clear explanation of some of the concepts behind UANA and USYSANA.

About UANA and USYSANA

    Your data model is stored in the dictionary tables (DICT conceptual schema/application model) UCTABLE, UCGROUP, UCFIELD, UCRELSH, UCKEY etc.

    When you analyze a conceptual schema/application model, the resulting compiled data model is stored in ULANA (* - see note).

    When you 'update USYSANA', the records are transferred from ULANA to USYSANA (which is in the TEXT conceptual schema/application model like UOBJ).  Not many people have even heard of this option.  In Uniface SIX when you see the main screen (with all the colours), use the Deployment pulldown menu, and look in the sub-menu, Distribution, there it is 'Update USYSANA'.

    In Uniface SEVEN from the Construction Workbench, go to Model, then use the File pulldown menu, there it is 'Update USYSANA'.

    Transfer the entity definitions you want your users to have access to from ULANA to USYSANA.  You should ship USYSANA *not* ULANA to your clients since it resides on the $UUU path and because it only contains the definitions you want to send.  It is not really advisable to just ship your compiled .frm's since the copy of the ULANA definitions they contain is not really mentioned anywhere in the Uniface documentation.  In Uniface Seven the reasons become a lot clearer (more on that in a minute).

    In Uniface Seven, you can use the /urr switch to copy the contents of ULANA or USYSANA to a .urr file (this is the equivalent of the .dol file for the UOBJ table).  eg: $idf /urr USYSANA.

    Now in Uniface SEVEN you also need to do this for component signatures. When you compile a form/report/service it generates a 'signature' into ULANA.  You then move the component signature (from the Component editor - ie: edit a form/report/service look in the File pulldown menu) from ULANA to USYSANA.  If you dont ship ULANA or USYSANA or a .urr file with your Uniface Seven application then your forms wont 'activate' (I think they will run but not activate...).

    Component signatures are also transferred into the .urr file if you create it ($idf /urr usysana|uana).

    March Hare Pty Ltd specialise in Uniface consulting, professional services component creation, Uniface web development and currently have some tools for sale on their web site at http://www.march-hare.com -- Remember all our tools come with complete source code.

Arthur Barrett
March Hare Pty Ltd
 

Note: * OULANA etc are overflow tables generated by Uniface.
 
 


Copyright © 1999-1999  $UUU  All rights reserved.
Disclaimer. | Site Comments.