shijilesh
asked on
ORCA Powerbuilder import
Hai all,
I would like to develop an application to export powerbuilder objects from pbl to text
file and import back to powerbuilder pbl , power builder support export library built in function to export but importing is not available. i tried ORCA but its always gives errors
could any one give me a sample code to import
thanks
I would like to develop an application to export powerbuilder objects from pbl to text
file and import back to powerbuilder pbl , power builder support export library built in function to export but importing is not available. i tried ORCA but its always gives errors
could any one give me a sample code to import
thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
One last suggestion. :)
If you're just trying to do this one time for one big project, and won't be doing it over and over again on an ongoing basis, you can do this.
First, make a separate folder under your main application's source folder for each PBL file and put the PBL in that folder.
So Instead of C:\MySource\ having 15 PBL files, your library list will look more like this:
C:\MySource\MyMainApp.PBL;
C:\MySource\MyCoolLibrary1
C:\MySource\MyCoolLibrary2
C:\MySource\MyCoolLibrary3
C:\MySource\MyCoolLibrary4
Then you can go to each PBL 1 time each and highlight all objects and export to the folder where the PBL is in.
Then you can make whatever changes you want to make to the files.
Then you can again go into PB and right click on each PBL 1 time and then highlight all the files again for that folder and import them at once.
So if you have more than about 40 PBL this could be a pain, or if you have to do this frequently, also a pain, but if this is just for one time thing or seldom, this is easier than trying to write an app to do it or setting up source control with MSSCCI or whatever.
If you're just trying to do this one time for one big project, and won't be doing it over and over again on an ongoing basis, you can do this.
First, make a separate folder under your main application's source folder for each PBL file and put the PBL in that folder.
So Instead of C:\MySource\ having 15 PBL files, your library list will look more like this:
C:\MySource\MyMainApp.PBL;
C:\MySource\MyCoolLibrary1
C:\MySource\MyCoolLibrary2
C:\MySource\MyCoolLibrary3
C:\MySource\MyCoolLibrary4
Then you can go to each PBL 1 time each and highlight all objects and export to the folder where the PBL is in.
Then you can make whatever changes you want to make to the files.
Then you can again go into PB and right click on each PBL 1 time and then highlight all the files again for that folder and import them at once.
So if you have more than about 40 PBL this could be a pain, or if you have to do this frequently, also a pain, but if this is just for one time thing or seldom, this is easier than trying to write an app to do it or setting up source control with MSSCCI or whatever.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
You would make your application's Workspace have source control pointing to the MSSCCI provider, and then tell to keep the objects on disc. Then You would right click the target I think, and tell it to put all objects in source control, which will go through every PBL and export all of the objects to text files and imports them to the source control provider. Then you can also check out all the objects at once. Now go to the source control folder where it saves your local copies and make whatever changes you need to make, and check in with the source control. Then "get latest" from PB and it will import the new code to the PBL.
It might help us offer more suggestions if we knew what the reason you were trying to do this was, there may be other solutions that are easier.