-2

I have a project and i want to have more control with the changes. For example:

Tom have w_principal with checkout Scott need to make changes to the w_principal file.

I want you not to be able to checkout before tom checkin

Marco Mireles
  • 53
  • 6

2 Answers2

1

According to this article (Checking objects out from source control), by default when you check out an object in PowerBuilder, it will locks the object in the archive so that no one else can modify it—unless your source control system permits multiple user checkouts

For TFVC, in Visual Studio we can set the lock type to prevent others check-out if using the server workspace.

So, you can check if there's the context options/ways in PowerBuilder to set the lock types against the server workspace. If no such options, then I'm afraid it's not supported.

BTW, you can take a look at below articles for “best practices” suggestions for using PowerBuilder in source control:

enter image description here

Andy Li-MSFT
  • 28,712
  • 2
  • 33
  • 55
-1

More than one user shouldn't be able to check out an object at a time. You just need to put your project into Source Control. The built-in Source Control in PB should give you everything you need.

Shenn Sellers
  • 172
  • 2
  • That's not necessarily true. TFVC supports checking out files without locking them. Exclusive locks can be configured but can only be enforced via the user of server workspaces. – Daniel Mann Jan 29 '18 at 20:37
  • 1
    Native PB source control should only be used with very small, trivial projects. – Matt Balent Jan 30 '18 at 12:32