Hi Uli,  Maybe I'm misunderstanding. Did you used to expose the counter maintenance dialog within your application so that it could be used by your customers to set counters? Or did you run the IDF against a production environment?

Hi Iain, do we agree that there are usecases from our customers who insists they can do adjustments/resettings of counters (end-of-year,...) ?

Where were you using this dialog such that it could affect production environments. Surely you aren't running an IDF against the live config? 

Hi Iain, in U10.3 the old U9 Counter Maintenence Dialog is NO LONGER provided, so each uniface customer has to implement his own maintenance. The missing UPC showed up in the first testrun retrieving counters. As we are all aware, it's an old uniface tradition that all PK fields in the metadictionary are UPC. The delivered extension of the U10.3 metadictionary for UOBJ.TEXT breaks this heritage.

Yes, but if you are exposing the IDF to them to do this, it seems wrong. Can you call this dialog from inside an app? I'v enot used it myself (since we ship to many customers, I can't have a central database model (TEXT) with counters in it or I might overwrite the customer data and mess everything up. I suppose I am wondering how you get an IDF level dialog running in a production environment, and whether the counter names are sufficiently clear as to be left to customers to modify...    Iain

Iain, as Uniface BV does not migrate the UUCNTR20 dialog to U10.3 I think we can stop this discussion.