Hi Luigi, thank you for your suggestion (and the note that it works on 9.7). That reminds me that Uniface works on "first fit", so we have to see that the merged ASN in memory will have the special line BEFORE the more general one. Therefore we have to repeat the more general line after our amendment usys:usyssql.frm usys:usys*.frm My first try on U10 failed, but I will investigate on this suggestion. Perhaps someone else has already experienced how to do it in U10; Thanks again, Uli

Hi Uli, maybe the answer to the problem is contained in these sentences of the U10 manual : First sentence

classic deployment

  Second sentence File Assignments and Redirection

File Assignments and Redirection

  Nothing about Frm files. Luigi

Hi Luigi, looks like even in U97, opening a form first looked at the [files] ASN and continue it's work with the modified name (that's why your 9.7 works). I assume this intermediate step will no longer been done in U10 and they go straight to the resources. Well the facts tells us, that the existing way is not supported any more. So we can not provide these benefits to our users/customers when going U10. Thanks a lot for doing all the work scanning the U10 manuals, Uli

What are the $search_resources settings in your asn? 

Hi Iain, in U10 you have no alternatives, the latest U10 helpfile (f114) reads:   $SEARCH_RESOURCES

$SEARCH_RESOURCES

Hi Uli, I feel/think "standard deployment" it is involved here, not only for U10 but also with U97... My expectations: - Case1: specialization [FILES] ABC.frm   ABC_DE.frm it should open ABC_DE.frm from your standard frm directory - Case2: substitution [FILES] usys:usyssql.frm   sys_sql.frm it should open sys_sql.frm from your standard frm directory The trick IMHO is to avoid paths to have standard deployment to work the way it is designed to do. Hope it helps... Gianni

Hi Gianni, thanks for your example, I will have a look this evening what it will do with U10. Greetings from Frankfurt/Germany, Uli

Hi Gianni, on U10201-f113 I gave it a try with

[FILES] usys:usyssql.frm aa3.frm

but still the standard SQL workbench comes up in in the IDE.   Looks like we overlooked something, perhaps someone else has another suggestion? TIA, Uli

Hi Uli, I have not the U10 version and I did a test with U97 and it worked perfectly. All my compiled forms are into : d:\\svil_97\\frm My asn : [FILES] ........................................................... usys:usyssql.frm    d:\\svil_97\\frm\\sys_sql.frm usys:usys*.frm          usys:usys*.frm ........................................................... ........................................................... ...........................................................  abc.frm          d:\\svil_97\\frm\\abc_de.frm *.frm                d:\\svil_97\\frm\\*.frm Luigi

I'm currently not working with uniface 10, but I would try the following Did you try the [RESOURCES] section? Just use different resources files, while the one with your variations should stay first (and of course the correct $search_resources setting). Wolfgang

That is what I was going to suggest.  If your top resource setting is  [RESOURCES] idf_mods usys...uar   where idf_mods is a folder with the correct structure, and forms with the same name as the ones Uniface uses, then it should use those in preference. 

Can you not compile them as ABC_XXX and copy them to ABC.frm on deployment?  I am now using the urm copy/move function to create my own UARs simply and using scripts, meaning its relatively simple to organise. 

Hi Iain, well, creating a form with the same name as the uniface one is a "very dirty" option, but it works (thank you). I tried to avoid interfearing too much in "the Labs" realm all those years, but it looks like U10 forces this way. And for my file replacement with the alternatives ABC.frm    ..\\frm_directory\\ABC_DE.frm this means that I have to use another construct: My actual way would be implementing ABC.frm as a dispatcher which reads a logical and activates the final form. Will cause some change in migrations from U9 to U10 converting the [FILES] section into a [LOGICALS] but it's a one-time effort. But if someone knows a way to keep "the old ASNs" alive; I would prefer this compatibility solution. Greetings from a very cold Frankfurt/Germany ('winter is comming'), Uli

gypsilon said I'm currently not working with uniface 10, but I would try the following Did you try the [RESOURCES] section? Just use different resources files, while the one with your variations should stay first (and of course the correct $search_resources setting). Wolfgang  

Hi Wolfgang, the problem with all these resource files is that the form in all the variations (former ABC_DE.frm) have to have the same name (ABC.frm). It makes development a real chaos because for every variation, you need a separate development environment. Gruß aus Frankfurt, Uli