I need to perform a large update to Clipper code and thought it would be easier to use #translate or #xtranslate.
I have a field I need to change the name on.
I need to change:
dbname1->fieldname1
to:
dbname1->fieldname2
I figure out how to do the simple version and just reference the field name, but I am concerned about the impact.
#xtranslate fieldname1 => fieldname2
Does anyone know the sytnax to include the ">" as part of the translate matchPattern?
This syntax does not work:
#xtranslate '>ownconstate' => '>ownconstat'
On Tue, 24 Jul 2018 08:46:41 -0700 (PDT), John Ward wrote:
I need to perform a large update to Clipper code and thought it would be easier to use #translate or #xtranslate.
I have a field I need to change the name on.
I need to change:
dbname1->fieldname1
to:
dbname1->fieldname2
I figure out how to do the simple version and just reference the field name, but I am concerned about the impact.
#xtranslate fieldname1 => fieldname2
Does anyone know the sytnax to include the ">" as part of the translate matchPattern?
This syntax does not work:
#xtranslate '>ownconstate' => '>ownconstat'
Hi John!
have you tried with:
#xtranslate dbname1->fieldname1 => dbname1->fieldname2
Regards
Damir
is upfront)
I need to perform a large update to Clipper code and thought it would be >easier to use #translate or #xtranslate.
I have a field I need to change the name on.
I need to change:
dbname1->fieldname1
to:
dbname1->fieldname2
I figure out how to do the simple version and just reference the field
name, but I am concerned about the impact.
#xtranslate fieldname1 => fieldname2
Does anyone know the sytnax to include the ">" as part of the translate matchPattern?
This syntax does not work:
#xtranslate '>ownconstate' => '>ownconstat'
I haven't seen a reference to the PP in over 18 years :-)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 239:21:57 |
Calls: | 6,624 |
Files: | 12,172 |
Messages: | 5,320,000 |