1. Andres Slachevsky
  2. PowerBuilder
  3. Wednesday, 31 January 2024 11:21 AM UTC

Hello All

 

Following the sample in the docs

 

Blob lblb_data
String ls_Base64Str

lblb_data = Blob("Test Base64", EncodingANSI!)

CoderObject lnv_CoderObject
lnv_CoderObject = Create CoderObject

ls_Base64Str = lnv_CoderObject.Base64Encode(lblb_data)


this works ok running from PB IDE

but in the 32 bits exe the ls_Base64Str returns null
if we compile the exe in 64 bits it works

is any dll missing or some othe component
we have a customer that can not migrate to 64 bits cause they have many 32 external Dlls and some DBF files with ODBC

using PB2017 R3
 
Andreas Mykonios Accepted Answer Pending Moderation
  1. Wednesday, 31 January 2024 12:20 PM UTC
  2. PowerBuilder
  3. # 1

Hi.

I'm testing the code you mentioned as follows:

Blob lblb_data
String ls_Base64Str

lblb_data = Blob("Test Base64", EncodingANSI!)

CoderObject lnv_CoderObject
lnv_CoderObject = Create CoderObject

ls_Base64Str = lnv_CoderObject.Base64Encode(lblb_data)

messagebox("", ls_Base64Str)

I'm using PB 2017 R3 1951. Build a 32-bit exe. Run it and get the result:

What is the exact version of Powerbuilder 2017 you are using?

Also have in mind that PB 2017 is EOMM...

Andreas.

Comment
  1. Andres Slachevsky
  2. Wednesday, 31 January 2024 12:31 PM UTC
We are using the same version

that is why i believe that there is some component missing
  1. Helpful
  1. Andreas Mykonios
  2. Wednesday, 31 January 2024 12:42 PM UTC
Are pbCSI170.dll and pbCSI170.dll deployed with your executable?

Andreas.
  1. Helpful 1
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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.