Hi, 

There is no need for /URR any more. However, you should ensure your $resources_output folder/uar is included in the [RESOURCES] section of the asn for your test environment.  

Hi Joanne,

adding to Iain answer: signatures are saved into "$resources_output\\sig" folder.

Regards,
Gianni

Hi Joanne

Gianni and Iain already said the importend things
I would like to contribute the following

In UF9 all globalen objects are collected in UOBJ.DOL and all signatures are collected in UDESC.URR
This are two ZIP-Files like UAR-Files but are created by /DOl resp. /URR
Disadvantage was, that they are not "hot plug" enabled. You have to close all IDE.EXE  /UNIFACE.EXE to replace them
All other objects are writen to distinct folder which could be different for all kinds of objects and even depending on the name of the object.
See the [FILES] section in the ASN-File

In UF10 all resources could be output to a folder or to an UAR-file which is also a ZIP-file
But for UnifAce complied objects  you can only specify the parent folder. The "internal" structure has to follow the UnifAce rules.
I.e  FRMs goes to .\\frm, APSs goes to .\\aps, .... , SIGs goes to .\\sig, .....
If you use UAR, then you have to specify the UAR-path/filename
UAR are still not updatable if it is open to another process but you can add UARs in th ASN-files which will the read in the order in the ASN file
If your ouput goes to a plain folder, every developer can write every time the news objects to this folder.

We do have the follwing ASN-file (simplified)

Ingo

== Part of the ASN-file ==

[SETTINGS]
; Set the output of newly created objects. 
; Under this folder there are many sub folders like frm, aps, ..., sig, ...
$RESOURCES_OUTPUT = \\\\Server\\environment_path\\resources_output

[RESOURCES]
;UnifAce reads the objects in this folders:
;We do have a few folders here
; This ist the "normal" folder. 
;  If you do nothing more with the folders, this is the only folder you need
\\\\Server\\environment_path\\resources_output
; Not all objects are to be deployed to our customers.
; So before delivering the object we run a special program which
; copies all "internal" into another folder
\\\\Server\\environment_path\\resources_output_intern
; This are some utility-components for the IDE
\\\\Server\\environment_path\\utilities.uar

[LOGICALS]
; To split the set of object into different folder, the programm needs to know where are the folders:
;  (Yes, you could scan [RESOURCES], but is not as safe as to define explicit the folders :-) )
RESOURCE_OUTPUT_deploy \\\\Server\\environment_path\\resources_output
RESOURCE_OUTPUT_intern \\\\Server\\environment_path\\resources_output_intern

[FILES]
; In UnifAce 10 there are still "normal" files, not to be treated as UnifAce objects for UARs
; these are list-files, symbol-files and compiled component structurs for the IDE
; BTW the the 'nice' renaming of LST and SYM-files
*lst    \\\\Server\\environment_path\\x_lst\\*.lst
*sym    \\\\Server\\environment_path\\x_sym\\*.sym
*.cmi   \\\\Server\\environment_path\\x_cmi\\*.cmi

When components are compiled, signatures are automatically created as .sig files in the $RSO path.

You can also force the creation of signatures using the command line switch /sig.

You can create a single signature or you can create multiple signature files using additional parameters with /sig switch.

This is what I have in my ASN file:

. . . 
[RESOURCES]

c:\\mirion\\uniface\\resources

. . . 

And then the folder structure under the resources folder has: aps, dtd , . . . sig . . . 

Since this is development, I am not using a UAR for the application.  The signature for my new form exists in the SIG folder

I am an idiot!  After reading everything below and believing I have things set up correctly, I went back into the menu to see what I was trying to activate and sure enough, I had a bad form name.  Thanks for all the edification though!