Missing "repversion" in xml files when using ide /cpy (workaround at the bottom)

Forum|Forum|5 years ago
April 16, 2020
17 replies
0 views

Anonymous

Hello,

With Uniface10.3 to export an object in a xml file using ide /cpy we can no import it using ide /imp.

The problems seems related to missing "repversion="6" in xml file. Why is this information missing in the export file ?

→ With ide /cpy xml contrains :

→ When exporting using Uniface 10.3 UI we get the xml file :

and importing with Import menu is OK

We need to export and import data using command line instructions as we do since many many years with Uniface older version.

Here Under an extract of Helop file for Uniface 10 :

~~Does some one have a solution ?~~

→ SOLUTION (thank's Ingo) : using /cpy to export data and using /cpy again with source as xml like here Under :

For export using ide

"/cpy 'DEF:MyTable.*' MyData.xml idf:"

For Import using ide ::

"/cpy xml:MyData.xml idf:"

Bye

Gianni Sandigliano
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hello,

With Uniface10.3 to export an object in a xml file using ide /cpy we can no import it using ide /imp.

The problems seems related to missing "repversion="6" in xml file. Why is this information missing in the export file ?

→ With ide /cpy xml contrains :

→ When exporting using Uniface 10.3 UI we get the xml file :

and importing with Import menu is OK

We need to export and import data using command line instructions as we do since many many years with Uniface older version.

Here Under an extract of Helop file for Uniface 10 :

~~Does some one have a solution ?~~

→ SOLUTION (thank's Ingo) : using /cpy to export data and using /cpy again with source as xml like here Under :

For export using ide

"/cpy 'DEF:MyTable.*' MyData.xml idf:"

For Import using ide ::

"/cpy xml:MyData.xml idf:"

Bye

Hi Pascal,

starting from Uniface 4.0.q6 (my first Uniface version), I had always approached data interchange as:
- after doing an export from source you can use import to destination (for Uniface repo objects)
- after doing a /cpy from source you should use /cpy to destination (for user data)

So, doing /cpy from source and using import to destination is IMHO a "mix not match" situation.

Is there a specific reason to use import after a /cpy or it is just a consolidated habit?

Gianni

PillarOfWisdom1: Inject yourself with some fantasy to NOT die of realityPillarOfWisdom2: The secret for a long healthy life is: eat half, walk double, laugh three times and love without measure! (Chinese saying)PillarOfWisdom3: Barcollo ma non mollo!

Ingo Stiller
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hello,

With Uniface10.3 to export an object in a xml file using ide /cpy we can no import it using ide /imp.

The problems seems related to missing "repversion="6" in xml file. Why is this information missing in the export file ?

→ With ide /cpy xml contrains :

→ When exporting using Uniface 10.3 UI we get the xml file :

and importing with Import menu is OK

We need to export and import data using command line instructions as we do since many many years with Uniface older version.

Here Under an extract of Helop file for Uniface 10 :

~~Does some one have a solution ?~~

→ SOLUTION (thank's Ingo) : using /cpy to export data and using /cpy again with source as xml like here Under :

For export using ide

"/cpy 'DEF:MyTable.*' MyData.xml idf:"

For Import using ide ::

"/cpy xml:MyData.xml idf:"

Bye

Hi Pascal
Did you try:$ude("export",ObjectType,ObjectProfile,{ZipArchive:}Filename {,OptionList} )
Okay, for using this, you can't use IDE and the comandline (CL)

Workarounds:
You can write a little APS with accepts arguments and does $UDE(...)
You could load the XML, insert the missing attribute and then to store again 🙂

@Gianni
Never get any problem by doing a mixed export/import
The differnence between UI and CL is, that with /cpy you can only copy separte tables why with UI you copy the whole object including all necassary tables

But with /apf /cpy on can also build a "container" with all tables you need

While writing this down, I could imagine whats happens

If you use the UIL, you export "objects" from a repository
If you use the CL, you export independent tables, which could not even from a repository

So UniAfce but the "reposiroy version" only into the output, when UnifACe is sure, that it is from the repository. UnifAce could simple check this by compare the table name to the list of reserved table names. And then a lookup into table UDICTVER (version info)

Or you got a extra switch /rpv=6

The question is: Bug or a Feature 🙂

Ingo

DanielIseli
Rocketeer
Forum|Forum|5 years ago
April 16, 2020

Hello,

With Uniface10.3 to export an object in a xml file using ide /cpy we can no import it using ide /imp.

The problems seems related to missing "repversion="6" in xml file. Why is this information missing in the export file ?

→ With ide /cpy xml contrains :

→ When exporting using Uniface 10.3 UI we get the xml file :

and importing with Import menu is OK

We need to export and import data using command line instructions as we do since many many years with Uniface older version.

Here Under an extract of Helop file for Uniface 10 :

~~Does some one have a solution ?~~

→ SOLUTION (thank's Ingo) : using /cpy to export data and using /cpy again with source as xml like here Under :

For export using ide

"/cpy 'DEF:MyTable.*' MyData.xml idf:"

For Import using ide ::

"/cpy xml:MyData.xml idf:"

Bye

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Ingo Stiller
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Hi Daniel

Okay UnifAce did already code my proposed "APS" 🙂

Thinking the last five minutes about the problem
Would not "/cpy xml:helloworld.xml idf:" also a solution?
As Pascal wrote, he use "/cpy idf:a_table.dict xml:helloworld.xml" to export one table (Am I right Pascal?)
The a simple copy will do the job, or?

Ingo

DanielIseli
Rocketeer
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Hi Ingo,

Uniface objects are usually stored in several tables (e.g. UFORM, UXGROUP, UXFIELD, ...). So, Computer says "No". Sorry.

In Unfiace 10 there is now a clear distinction between user data and development objects (i.e. repository data). In previous versions it was possible (probably unintentionally) to /cpy data from the database to an export file and use /imp for importing, or use the export form of the IDF and import everything with /cpy. In version 10 the user data needs to be exported/imported with /cpy or $ude("copy"), and development objects are exported with the Export facility of the IDE or $ude("export") and imported with /imp, the Import Facility of the IDE or $ude("import").

Daniel

Ingo Stiller
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Hi Daniel
It is clear that when you want to export/import a whole object (component with all its sub tables) you should use the import/export facilities of UnifAce

But Pascal wrote, the he use /cpy to export a table (e.g. UXGROUP)
And this XML could still be "imported" by "/cpy xml:uxgroup.xml idf:"
Or is this not longer possible?

Ingo

DanielIseli
Rocketeer
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

I don't think that is what Pascal meant.

And copying data from the repository tables is still "possible" as you describe, but it's not recommended (or should I say supported). If you want to corrupt your repository on purpose then that is probably a good start... :-\\

Daniel

Ingo Stiller
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

"Corrupt the repository"
We do this for over twenty years 🙂
Can you explain, why you can currupt you repository beside that you can miss a few tables to move by this "/cpy idf: xml:" "/cpy xml: idf:"
Are doing UnifAce some magic things when using /exp and /imp ?

I thougt till this morning, export is doing
Copy all rows from all tables necassary for an object <= Like "/cpy idf: xml:" resp "/cpy /apf idf: xml:"
And new, insert "repversion=xyz" in the XML-file

Import is doing
Import the header, check version (and new repversion)
Clear the old object (does UnifAce this really?)
Copy all rows in alle tables from the XML-file <= Like "/cpy xml: idf:"
If version ist not correct, start an migration tool

So if one is exporting/importing from/to the same UnifAce version is the same then /cpy
Okay, it could be that there residules from the old object, but thats all

Ingo

Anonymous
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Hi eveybody,

The goal for us is to export for example 1 table with corrected data and send the xml file to our customers. They only have to use the /imp command to load the table with our corrected data

And yes we are using same Uniface version with /cpy and our customer too.

it works fine with older Uniface versions (<=9.7)

Now we are trying to migrate our application from 9.7 to U10 and we are trying our tools but some of them they are not working anymore (for example out tool that use une ide /cpy to export a table)

Ingo Stiller
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Hi Pascal

Okay, the the solution is very simple 🙂
/cpy xml:esample_1.xml def:

instead of /imp

That's all

Gianni Sandigliano
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

... 🙂 🙂 🙂

Ingo Stiller
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Hi Gianni
Didn't you suggest this by your first answer 🙂

@Pasacal
If your customer still wants to have a /imp, just code a simple batch file which "converts" "/imp=$filename" to "/cpy xml:$filename def:"
The only thing your customer has to change is the name of the exetuable. 🙂

Ingo

Ingo Stiller
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hello,

With Uniface10.3 to export an object in a xml file using ide /cpy we can no import it using ide /imp.

The problems seems related to missing "repversion="6" in xml file. Why is this information missing in the export file ?

→ With ide /cpy xml contrains :

→ When exporting using Uniface 10.3 UI we get the xml file :

and importing with Import menu is OK

We need to export and import data using command line instructions as we do since many many years with Uniface older version.

Here Under an extract of Helop file for Uniface 10 :

~~Does some one have a solution ?~~

→ SOLUTION (thank's Ingo) : using /cpy to export data and using /cpy again with source as xml like here Under :

For export using ide

"/cpy 'DEF:MyTable.*' MyData.xml idf:"

For Import using ide ::

"/cpy xml:MyData.xml idf:"

Bye

** Deleted post ***

Ingo,

this forum is not the place to post stuff that is not related to the Uniface product.

Thanks,
Daniel

DanielIseli
Rocketeer
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

I can only stress that this is not the recommended way. In version 10 you should export/import development objects as described in my post.

And in case you encounter any problems with the way Ingo is describing the procedure then please call him instead of support. 😉 You wont get any guarantee that this will work in all circumstances and will continue to work in future releases...

Also, why does your customer have a repository? Normally you would provide the compiled development objects with the required correction to the end user. I've never received some C++ sources from Microsoft in case I need to correct a problem in Windows. :-\\

Anonymous
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Hi Ingo it seems to work with your /cpy command we need some more time to make more test.

So we will test using /cpy for export and /cpy to import we need to change our scripts and programs.

PS : It would have be nice and far more simple to have the repository version in the xml when exporting with /cpy 🙂

Ingo Stiller
Participating Frequently
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Hi Daniel
So how to export one table from one repostitory to another one 🙂
And this by UnifAce-tools, not by any external one

And please don' say this also not possible in language xyz
There should still a few advantages for UnifAce

Ingo

DanielIseli
Rocketeer
Forum|Forum|5 years ago
April 16, 2020

Hi Pascal,

You could use ude.exe, which is basically a command line utility for the $ude ProcScript function.

The syntax for ude.exe is:

ude.exe {/GeneralSwitch(es)} Operation Type Source {+ Source} {Destination} {-Option(s)}

The /GeneralSwitch(es) are the normal command line switches that are also used by (e.g.) the ide.exe, like /asn=, /ini=, /adm, ...

Here are some examples (for simplicity without /GeneralSwitch(es)):

> Export Component:

$result = $ude("export", "component", "MUSIC*", "musiccpt.xml")

Would translate to:

ude.exe export component MUSIC* musiccpt.xml

> Export Entity:

$result = $ude("export", "entity", "*", "sales_entities.xml", "model=sales")

Would translate to:

ude.exe export entity * sales_entities.xml -model=sales

> Export Global ProcScript:

$result = $ude("export", "proc", "G_ADD", "libprc_other.xml", "library=otherprocs")

Would translate to:

ude.exe export proc G_ADD libprc_other.xml -library=otherprocs

Please note that in ProcScript the profile character '<GOLD>+*' is used, but on the command line it's just '*'. The result is the same.

I hope this helps.

Daniel

Hi Ingo,

I'm not falling for this. There's no reason to do this (IMO). The recommended way is (as mentioned before) to export one development object from one repository and import it into another one. That's the way you do it. Just use the tool as it was intended by the lab. 😉

And Uniface still has a lot of advantages. Maybe it helps to learn something new once in a while, instead of insisting to always do it in the old way... 😜

No hard feelings...

Daniel

Recent badge winners

Sign up

Please log in or register:

Welcome to the Rocket Forum!

Please log in or register:

Scanning file for viruses.

This file cannot be downloaded