Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.
You are not logged in.
Pages: 1
Hi Chun,
I have uploaded an interim release that will you set import encoding from the command line.
I send mail to you with download instructions. If anyone else would like this release, please send a request to techsupport@ecrane.com.
Regards,
Phil
Hi there,
I have an existing PowerGen project GEN file and would like to make this project import using the HEXASCII option.
When I edit this file, what entry/value do I add/change ?
Thanks.
Chun.
Hi Chun,
This setting is saved in the Registry under HKEY_CURRENT_USER/Software/E. Crane Computing/PowerGen.../Preferences/ImportEncoding. Values are wither ANSI or HEXASCII.
Regards,
Phil
Hi Phil,
So this means that all my PowerGen projects must be either all HEXASCII or all ANSI/DBCS.
What if I have a mixture ?
Will having the setting on for HEXASCII affect any projects which are using ANSI/DBCS ?
i.e. we have projects prior to PB10 built using PowerGen, and if required we would like to re-build those projects using PowerGen.
Thanks.
Chun.
Hi Chun,
There are a couple ways to handle this:
1. The Registry setting is specific to a user account. So you could set up one "user" to be used for HEXASCII builds and another for ANSI.
2. The encoding option is only relevant to PB10 and later. Applications for earlier PB versions will always use ANSI, regardless of the Import Option.
3. We can add a command line parameter to set the option explicitly.
Let me know if any of these are acceptable to you.
Regards,
Phil
Hi Phil,
A command line option would suit our environment better, since we have scheduled builds that run everyday and the scripts would be easier to relocate to execute on any of our servers if required without any required registry changes.
It would be clear and easily identified within our batch scripts which encoding we are using.
Thanks.
Chun.
Hi Chun,
We'll put together an interim release that will have this feature. I'll be in touch directly and will also update this thread.
Regards,
Phil
Hi,
took me half a day realize that I have to set the ImportEncoding in PowerGen which leads me to the question why I have to set it at all? PowerBuilder stores the encoding in the exported files (HA at the beginning of the file)
Thomas
We were have problems with $$hex showing up in a ton of string literals and code comments. Changing the registry setting to HEXASCII seems to have fixed that problem, however, our build which used to take 40 minutes now takes 125 minutes. Is this normal behavior after when using HEXASCII instead of ANSI?
Hi Thomas,
Point well taken. It's on the list for the next maintenance release.
Regards,
Phil
As far as build times with HEXASCII is concerned, most of the heavy lifting of the build operation is done by PB DLLs (via the ORCA interface supplied by Sybase). There is no difference on the PowerGen side of the processing.
Regards,
Phil
Pages: 1