Browse DevX
Sign up for e-mail newsletters from DevX

Tip of the Day
Language: PowerBuilder
Expertise: Beginner
Jul 24, 1997



Building the Right Environment to Support AI, Machine Learning and Deep Learning

PowerBuilder lost scripts

We are working with PB 5.0.02 Enterprise with an Oracle server. The scripts are kept on a Novell server version 4.x.

We regenerate a PBL, and when we re-edit the object, one or more events will be missing. It only happens once in a long while, but when it does, it really hurts. We do frequent saves, and events that have previously been saved will also be gone at times.

Of course the best we can do when this happens is to get a day-old tape back-up from the server, small compensation for a day's work gone.

We are careful to exit the various painters using the prescribed exiting tool (door icon).

I have even used tools such as Ultra-Edit to look into the PBL after the events are lost, but before a reboot, and the code really is not there.

We have investigated size of objects, but we don't think this is the problem because we have objects that are larger than the one that just lost the scripts (events). The entire PBL is less than 1.5 MB.

Any idea why this is happening or, if it should happen again, how to recover lost work?

I have a few suggestions to help you out. I do not have experience using Novell servers, because my company migrated to NT several years ago, but I do recall an article in the PowerBuilder newsgroup that described a problem very similar to the one you are seeing. I have used the Deja News query service and retrieved the following reply to a question identical to yours:

On Novell, there are file attributes just like there are on DOS (with some extensions, of course). One attribute is the share attribute. To check/modify this, do the following:

  1. Go to a DOS prompt.
  2. Change directories to the directory where your source code is located.
  3. Type "FLAG *.PBL" and hit enter. This will give you a list of your PBLs and show you their attributes.
  4. Type "Flag *.PBL +s" and hit enter. This will add the share attribute to your PBLs (and you will see them).

Your PBLs are now shareable, and you will avoid the "Save Object Failed" culprit. Remember to do this after you a) create a new PBL and b) Optimize your PBLs (which in effect creates them as new).

The above article was posted by Bill Green.

If your corruption is related to a single object or group of objects, you can take a backup copy of the current set of libraries. Restore your old copy from the backup, then use a compare utility such as windiff or PBDelta to compare the objects and highlight the changes that were made to the object so far today. At least you will have complete reference of the "good" objects and their changes so you will only lose some of the day's work.

DevX Pro
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date