Hi Hassan;

  It's pretty straight forward as IM is technically basically PB "under the hood" - just with a different look & feel to the same IDE.

  So the PBL library in IM is the same as PB. All you need to do is have a shared PBL between IM and your PB IDE / PB App and they can access the same reports back & forth as an IM report is really just a DataWindow. The only main consideration is to make sure that you keep the PB & IM releases at the same version & build so that the Report / DWO's are technically the same source / runtime code (as this is a dependency).

HTH

Regards ... Chris

Hi, Hassan - 

To add to what Chris has said, you might want to look at the GetLibraryList, SetLibraryList, and/or AddToLibraryList PowerScript functions. These methods can be used to dynamically change the application's list of PBD's at execution type. Your app could "attach" a user's individual IM library, and/or an IM library shared by a team, department, or other organizational group, etc.

Best regards, John

Hello,

Thank you for all the help. 

I did the following steps and I am getting an error. Please let me know what went wrong and how to fix this.

1. I created a library (.pbl) in my application in powerbuilder.

2. I created a vc and a datawindow control with a generic (employee table) query.

3. I Added the library in Infomaker. (Now I am able to access the same datawindow from powerbuilder as well as infomaker).

4. I changed the query for this datawindow via infomaker (this is basically what I want the user to do eventually).

5. When I ran the powerbuilder app after saving this changed query and tried to access the grid (datawindow), it gave an error saying incorrect syntax

Cause of Error:

In powerbuilder, when I went to check the datawindow query (which should have been changed now due to infomaker change), It shows the following line instead of the changed query:

"cloud;MTcwMDYzOTQ4NQ==;3lLts6zGi1oMR9IN1KPJe4W1yLVU39BEP5z/uoPFXdM2DSfmxhBX3UoCg0SpHa/rp9ZqUyVmdcCfh7dFSYp68w=="

This causes the error.

How do I fix this?