Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Characters lost when working with VSS

  1. Issue
0
Votes
Undo
  1. Arcady Abramov
    Arcady Abramov
  2. PowerBuilder
  3. Thursday, 17 October 2019 07:57 AM UTC

Hello,

We have recently upgraded our system to PB2017 from PB12.5 and noticed an issues when working with VSS source control. There is an issue in exporting and importing of DW with UTF data hard coded in it.

When working with VSS, "SUB" character is lost when exporting/importing ( it does not show correctly on this page )

 

Before adding to SC

l�8*Pif FiiTVz¡!#￡+&*P￮U%~"(O7meva`y!_￦/`￡0j
.45n�&NN￴]G(0

After adding to SC and checking out:

l�8*Pif FiiTVz¡!#￡+&*P￮U%~"(O7meva`y!_￦/`￡0j
.45n�&NN￴]G(0

 //-------------UPDATE--------------------------

Regular export to HEX ASCII works correctly and the problem happens on export for SC

After adding file to SC and viewing it's text in SC itself, we can see that the "SUB" character is already missing

//--------------------------------------------------

  1. Export
  2. PowerBuilder (Appeon)
external function error
OLE with MS-Word: printout(FALSE)
Responses (2)
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Thursday, 17 October 2019 10:46 AM UTC
  2. PowerBuilder
  3. # 1

Hi Arcady, to ensure I get this one right:

Q 1 :: [Export] of the DataWindow object into a .SRD text file exports the characters correctly?
NOTE: You might see non ASCII characters convert into $$HEXxxxx$$ format.

Q 2 :: DataWindow source exported to source control has the non-ASCII characters represented DIFFERENTLY than in the regular "Export" file?

I'm trying to understand whether it is "extract source from .PBL" that has an issue -- or it is the API to version control -- or it is something specific to VSS (Visual SourceSafe I presume).

TIA / Michael

Comment
Load more comments
Michael Kramer
  1. Michael Kramer
  2. Thursday, 17 October 2019 11:22 AM UTC
Which to me looks like an issue in VSS's client. Not sure you will find a fix for that.

From PowerBuilder IDE there is no difference at all in working with WizSource or VSS. For the IDE they are both SCC providers accessed through the same API (MSSCCI).
  1. Helpful
Arcady Abramov
  1. Arcady Abramov
  2. Thursday, 17 October 2019 11:55 AM UTC
But we did not have this problem, when we were working with PB 12.5
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Thursday, 17 October 2019 12:50 PM UTC
With SCC API source control systems like VSS, PBNative, or WizSource, the IDE writes the object source to disk and then passes an array of filenames to the SCC provider. If one is handling it differently, it would likely be the fault of the provider.

Try a manual HEXASCII export from 12.5 an 2017 and compare the two files.
  1. Helpful
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Thursday, 17 October 2019 12:39 PM UTC
  2. PowerBuilder
  3. # 2
  • Working for one SCC provider but not another hints at one SCC provider being the reason for failure.
  • However appearing in PB 2017/2019 but not in PB 12.5 hints at this being PB version specific.
  • Appeon would need a test case to help them investigate. Copy the DW object to new, empty .PBL and verify issue remains.
    • IF NOT ==> Hints at issue inside .PBL file
    • Solution ==> Optimize .PBL. - or - Replace old .PBL file with new file.
  • If issue remains please create bug request. Upload new .PBL is test case for verification.

HTH /Michael

Comment
Arcady Abramov
  1. Arcady Abramov
  2. Thursday, 17 October 2019 12:45 PM UTC
Tried that already. The issue remains. I guess opening a bug request on this will be close to pointless. Who works with VSS nowadays? ...
  1. Helpful
Michael Kramer
  1. Michael Kramer
  2. Thursday, 17 October 2019 12:58 PM UTC
See Roland's suggestion to reply #2 (below).

You will be surprised how many remain on VSS because it suits their needs.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.