PB Native getting new window.

[codyli]

I have powerbuilder 10.5.1 Build 6537. Few computers are sharing on
the same Target and pbls. There is no problem for normal usage of
check-in/check-out/get latest version. However, when one of the users
added a new window object to a pbl and add it to source control. The
other users cannot see that window object while getting the latest
version on that specific pbl. When i logon to the server, the srw
file is in the server and the user who register it could see that dot
sign on his local machine as well. It only happen on window object.
When i do the same procedure on datawindow object, the other users
could get that new datawindow while getting the latest version.
Anyone know what the problem is ? Thank you.

Cody

[Paul Horan[TeamSybase]]

You're sharing the PBLs on the network? That's wrong. The PBLs go on your
local drives (each developer has their own copy of the source PBLs). The
PBNative project folder is the only thing that goes out on the LAN shared
drive.

When someone creates a new object, PB will do the following:
- Check out the .PBG file for the .PBL (it's got the same name as the PBL,
just with a .PBG extension)
- Add the entry for the new object
- Check the .PBG file back in and increment its version number.

Now, when someone else does a GLV on either the PBL or the Target, PB will
see that they're out of sync on the .PBG file as well, and bring down the
latest copy of that file. In there, it will see the entry for the new
object, and show that object name with a checkmark next to it in the GLV
dialog.

If that's not happening, check these things in the following order.
1. Look in the .PBG file on the object creator's machine. See if it
contains the entry for the new object.
2. Look in the .PBG file in the PBNative folder (out on the LAN). Look for
the same entry.
3. Look in the .PBG file on the other developer's workstation. Look for the
same entry.

Paul Horan[TeamSybase]

"codyli" <cody...@gmail.com> wrote in message
news:1175628269.2...@d57g2000hsg.googlegroups.com...

[codyli]

First of all, thanks for your reply.

I found that when i am adding or removing objects some pbls, it works
just fine, it updats the .PBG files. However, when i adding or
removing objects on the pbl i mentions yesterday, it does not update
the .PBG file at all. neither the local PBG nor the server's PBG.
Lets say when i am adding the new objec to the source, it return me
this warning.

Adding selected items to source control...
PB Native Status: Adding C:\[object_name].srw...
PB Native Status: Checking out C:\[pbl_name].pbg...
SccCheckout() failed because object is checked out.
PB Native Status: Reverting C:\[pbl_name]..pbg...
SccUncheckout() failed because object is not checked out.
Error checking in .PBG file. Verify that new entries are correct and
check in .PBG file manually.
C:\[object_name].srw version 1 successfully added to source control
Operation Completed

So it added to the source successfully with the dot next to the
object, but i cannot find the name of the object on .PBG file because
this file had never been updated.

It works fine on some pbls. Any clue about it? Is there any
solutions? By the way, i am not sharing the PBLs on network, so every
developer has their local copies.

Thanks in advance.
Cody

On Apr 3, 5:55 pm, "Paul Horan[TeamSybase]" <phoran AT sybase DOT com>
wrote:

> You're sharing the PBLs on the network? That's wrong. The PBLs go on your
> local drives (each developer has their own copy of the source PBLs). The
> PBNative project folder is the only thing that goes out on the LAN shared
> drive.
>
> When someone creates a new object, PB will do the following:
> - Check out the .PBG file for the .PBL (it's got the same name as the PBL,
> just with a .PBG extension)
> - Add the entry for the new object
> - Check the .PBG file back in and increment its version number.
>
> Now, when someone else does a GLV on either the PBL or the Target, PB will
> see that they're out of sync on the .PBG file as well, and bring down the
> latest copy of that file. In there, it will see the entry for the new
> object, and show that object name with a checkmark next to it in the GLV
> dialog.
>
> If that's not happening, check these things in the following order.
> 1. Look in the .PBG file on the object creator's machine. See if it
> contains the entry for the new object.
> 2. Look in the .PBG file in the PBNative folder (out on the LAN). Look for
> the same entry.
> 3. Look in the .PBG file on the other developer's workstation. Look for the
> same entry.
>
> Paul Horan[TeamSybase]
>

> "codyli" <codyli...@gmail.com> wrote in message

>
> news:1175628269.2...@d57g2000hsg.googlegroups.com...
>
>
>
> >I have powerbuilder 10.5.1 Build 6537. Few computers are sharing on
> > the same Target and pbls. There is no problem for normal usage of
> > check-in/check-out/get latest version. However, when one of the users
> > added a new window object to a pbl and add it to source control. The
> > other users cannot see that window object while getting the latest
> > version on that specific pbl. When i logon to the server, the srw
> > file is in the server and the user who register it could see that dot
> > sign on his local machine as well. It only happen on window object.
> > When i do the same procedure on datawindow object, the other users
> > could get that new datawindow while getting the latest version.
> > Anyone know what the problem is ? Thank you.
>

> > Cody- Hide quoted text -
>
> - Show quoted text -

[Chris Pollach]

I am not seing your problem on my PB 10.5.1 ... but I am on Build 6021 on
MS-Windows XP/MC and W2003 servers.

--
Regards ... Chris Pollach
Blog: http://chrispollach.pbdjmagazine.com
ISUG: http://chrispollach.pbdjmagazine.com/isug_membership.htm

"codyli" <cody...@gmail.com> wrote in message

news:1175694104.7...@w1g2000hsg.googlegroups.com...

[Paul Horan[TeamSybase]]

PBNative works by maintaining a "lock" file for each object. If you look in
the PBnative folder out on the LAN, you'll see a pair of files for each
object. For example, for a datawindow, you'd see myDatawindow.srd and
myDatawindow.srd.prp. The .PRP file is a simple text file that contains
two lines

Line 1 is the current checkout status. 1 = checked out, 0 = available.
Line 2 has more metadata. Current version, last checkin timestamp, and if
the object is checked out, who's got it.

Open the <PBL>.pbg.prp file. If Line 1 is set to 1, change it to 0 and save
the file. (You may have to fiddle with the file attributes because they're
marked as read-only).

Paul Horan[TeamSybase]

"codyli" <cody...@gmail.com> wrote in message

news:1175694104.7...@w1g2000hsg.googlegroups.com...

[codyli]

Got it, it works fine after i clear the pbl checkout. I don't know
how that got locked by the other user, but it work find right after i
clear that lock. Thank you so much problem solved.