• You are here:  
  • Home
  • Q&A
  • Q&A
  • InfoMaker
  • Infomaker R2 and Powerbuilder R3 compatibility

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

Resolved Infomaker R2 and Powerbuilder R3 compatibility

  1. Advice
0
Votes
Undo
  1. Rachid Sbaibi
    Rachid Sbaibi
  2. InfoMaker
  3. Friday, 27 September 2019 09:14 AM UTC

Hi all,

Does anyone knows if Infomaker R2 is compatible with Powerbuilder R3 1880.

Regards.
Rachid.

Clipping Issue with column over two pages.
InfoMaker Version Migration
Accepted Answer
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 10:58 AM UTC
  2. InfoMaker
  3. # Permalink

It depends! (sorry, but it does)

Hence, ==> You should test specific DataWindow objects in question.

I expect you question PB 2017 R3 vs. IM 2017 R2 ==> R3 adds properties unknown to R2. So, code modified by R3 will potentially fail in R2.

HOWEVER ==> All DataWindows still not modified behave like usual. Compile/migrate for 2017 R3 doesn't change source of 2017 R2 - as long as we talk DataWindow objects.

ALSO ==> IF your DataWindow calls global functions then R2 will definitely risk problems since now we are talking about running R3 compiled code on R2.  In general that is a big no, No, NO, NO!

AND ==> There is ALWAYS risk trying to open/run .PBL files compiled for different release. You need to test in your specific environment that your specific release change doesn't render the compiled code unreadable.

Anybody (like me) may direct you on anything but no recommendation beats testing!

HTH /Michael

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 27 September 2019 16:59 PM UTC
Hi Michael;

Thanks for the great answer!

et Al ... the basic rule is NEVER "Mix & Match" PB / IM versions. You are taking a big risk that your DW (aka Report objects in IM) will be updated and then not work properly between the products!

Regards ... Chris
  1. Helpful
Michael Kramer
  1. Michael Kramer
  2. Saturday, 28 September 2019 11:53 AM UTC
THX, Chris

NOTE on specific scenario = "customer creates DW in R2, app runs on R3"

Export DataWindow from IM R2; then import into PB R3 app's PBLs/PBDs.

This may already be modus operandi.

That way, R3 code can't wreck the PBL that IM R2 depends on.

And IM R2 can't ruin whatever is in the PBLs/PBDs that the app depends on.
  1. Helpful
There are no comments made yet.
Responses (3)
Rachid Sbaibi
Rachid Sbaibi Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 12:18 PM UTC
  2. InfoMaker
  3. # 1

Thanks Michael,

We deliverd a 2017 R3 powerbuilder application to our customer. The customer overload our datawindows by his own datawindows designed under Infomaker R2. But he is unwilling to step from Infomaker 2017 R2 to R3. 

If he have to change his own datawindows, he'll sure do it with ann R2 infomaker. But I will strongly recommend him a migration to R3.

Regards.
Rachid.

Comment
Michael Kramer
  1. Michael Kramer
  2. Friday, 27 September 2019 14:08 PM UTC
The "major" enhancements in R3 for DataWindows is increased security features in NativePDF. New properties are:

* Export.PDF.NativePDF.UserPassword

* Export.PDF.NativePDF.MasterPassword

* Export.PDF.NativePDF.Restrictions
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 23:10 PM UTC
  2. InfoMaker
  3. # 2

Just FYI, I am required to keep 2 version of the reports PBL that we use - one in PBv10 and on in PBv12.  THjis is because we use the old IMv10 that had a perpetual license and did not require SYSAM.

It's a clean and simple setup, and as long as you keep track of which DWO goes into which PBL, you are golden.


Olan

Comment
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.