Uniface User Forum

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob

Hi Robert

I'm not 100% sure want you want to do, but "to inject" a variable into a compiled component is a no go.
The "variables" are compiled and stored with a kind of P-Code into the whole compiled from.

What may possible (I'm mot sure) ist to add a variable in the IDF (the source code of the component) like "VERSION_NNNN", after compiling (without ZIP) one can search for the string "VERSION_NNNN" in the compiled P-Code and replace it with "VERSION_1234". But be carefull, do not change the length.

But why not change the version info in the repository?
Is the "problem" that it is only clear which version it is after compiling and at the moment of creating the UAR file?
A solution would be a little (UnifAce) program to search for "VERSION_XXXX" (short before creating the UAR)  in the variable declaration section of a compont and then replace this variable name, and the compile it.
Or another solution would be to store the compile-datetime in a variable of the component. (either by a little UnifAce programm or a "manipulated" view of the source code). Then create a new small table (which is also delivered) that contains the dates on which the UAR files are created. Or you can rely on the dates of the UAR creation.
Then you can compare the variable with the compile date against the list of UAR dates and know in which the component was (is not 100% watertight, but an approach)

Ingo

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob

Some immediate thoughts:- 

1)

Why not change the repository of a backup..... 

create a backup of DICT....

update uform

comile to uar

2)  Identical to option 1, export to xml, then modify the xml, compile to uar

3) Another idea, if you have a central point for your activate statement... change that to incorporate a version in the $instancename

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob

Hi Osman,

I have played with the uform update, our IDE is using overflow tables so an update is very tricky

Rob

Some immediate thoughts:- 

1)

Why not change the repository of a backup..... 

create a backup of DICT....

update uform

comile to uar

2)  Identical to option 1, export to xml, then modify the xml, compile to uar

3) Another idea, if you have a central point for your activate statement... change that to incorporate a version in the $instancename

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob

Hi Robert, 

Uform will work fine at the beginning of the EXEC trigger

You could also add code like #defines Version = <InjectVersionHere > to every component and use sql to update uform and oufrom

or, you could use option 2 and replace the xml (so you are not reliant on overflow tables)

but, all suggestions would be to change a copy of the source

Hi Osman,

I have played with the uform update, our IDE is using overflow tables so an update is very tricky

Rob

Some immediate thoughts:- 

1)

Why not change the repository of a backup..... 

create a backup of DICT....

update uform

comile to uar

2)  Identical to option 1, export to xml, then modify the xml, compile to uar

3) Another idea, if you have a central point for your activate statement... change that to incorporate a version in the $instancename

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob

If this is to be used occasionally (e.g. for debugging or occasional error reporting) then there is another approach. 

You could use $assignments("RESOURCES"), (which doesn't appear to be documented) to get the list of uar files (and folders) deployed. 

A loop through this list, looking for $fileexists (you'd have to determine the file type from the componenttype and add the folder and suffix) which stopped at the first match would give you the file name of the UAR that file was loaded from. 

Slower than having it compiled in, but 0 developer maintenance. 

Regards, 

Iain

Hi Robert, 

Uform will work fine at the beginning of the EXEC trigger

You could also add code like #defines Version = <InjectVersionHere > to every component and use sql to update uform and oufrom

or, you could use option 2 and replace the xml (so you are not reliant on overflow tables)

but, all suggestions would be to change a copy of the source

Hi Osman,

I have played with the uform update, our IDE is using overflow tables so an update is very tricky

Rob

Some immediate thoughts:- 

1)

Why not change the repository of a backup..... 

create a backup of DICT....

update uform

comile to uar

2)  Identical to option 1, export to xml, then modify the xml, compile to uar

3) Another idea, if you have a central point for your activate statement... change that to incorporate a version in the $instancename

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob

Hi Iain,

Sounds like a great plan, I'll try it out.

Thanks

Rob

If this is to be used occasionally (e.g. for debugging or occasional error reporting) then there is another approach. 

You could use $assignments("RESOURCES"), (which doesn't appear to be documented) to get the list of uar files (and folders) deployed. 

A loop through this list, looking for $fileexists (you'd have to determine the file type from the componenttype and add the folder and suffix) which stopped at the first match would give you the file name of the UAR that file was loaded from. 

Slower than having it compiled in, but 0 developer maintenance. 

Regards, 

Iain

Hi Robert, 

Uform will work fine at the beginning of the EXEC trigger

You could also add code like #defines Version = <InjectVersionHere > to every component and use sql to update uform and oufrom

or, you could use option 2 and replace the xml (so you are not reliant on overflow tables)

but, all suggestions would be to change a copy of the source

Hi Osman,

I have played with the uform update, our IDE is using overflow tables so an update is very tricky

Rob

Some immediate thoughts:- 

1)

Why not change the repository of a backup..... 

create a backup of DICT....

update uform

comile to uar

2)  Identical to option 1, export to xml, then modify the xml, compile to uar

3) Another idea, if you have a central point for your activate statement... change that to incorporate a version in the $instancename

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob

Hi Robert,

why do you want to inject a Variable?

Why not a operation OP_Get_Version?

You just have to inject only once a "#include MY_LIBRARY:MY_OPERATION" into the Script Container of each Form/Service/Report.

In MY_LIBRARY:MY_OPERATION you can write a operation like this:

You can now change the injected Text as you like.

You only have to change the Text in Table UINC per SQL:

update UINC

set ucomment = '<unimeta><UTEXT>operation OP_Get_Version

Kind regards

Norbert

Hi,

Is it possible (without changing the IDF repository) to add a new local variable to every component in a U10 IDF?

When Uniface components are deployed in UAR files, it seems impossible to find out which UAR file the component was actually loaded from.

In our application we have projects, in the idf each project version is identified by a project suffix e.g. a form names TEST may have 10 variants like TEST_P0001, TEST_P0002 ...

Each of these forms will be deployed in a project UAR file named after the project P0001.uar or P0891.uar but will be named TEST.FRM in each uar file the only way to find out the variant is to activate the form as query $componentname or display the component name in the title bar or any other way you can think of, for services that will not work.

I want to inject a local variable in every component 

string VERSION_<the comp version>

then in query form, run cod as below were "P_comp  would be a param in

newinstance P_comp,"getversion" 

$1 = $componentinfo("getversion","VARIABLES")

The variables will have the list of local variables including the injected VERSION_P0001

I could inject the code directly in SQL or export the components, inject the code into the XML export file and reimport, both these are tricky and problematic. 

Is there a safer way to do this?

Can the UAR where the form is run from be identified?

Thanks for reading if you got this far :)

Rob