It was a network issue but I have not the solution.

Now we are able to work directly on the network as before.

Thank you for your replies.

Thank you for your reply.

We are a small team of 5 developers we are developing and correcting our application locally but the master copy is on a common network drive, and we have to report the modification. We are working like this since many years, about 20 years :). And it was acceptable. But since 2 months it becomes very long to modify common network sources. During this period there was Powerbuilder 2017, Windows 10 evolution of our laptops, and network domain modification by the IT. So we don't know where is the problem.

Never run PowerBuilder with libraries on the network.

If you are concerned with backups, place the workspace under your documents folder and make sure that your profile is being saved to the network when you log out, or just run an automatic backup tool.

This is both a network issue and a PB issue.

Normally, it's a TERRIBLE idea to have your PBLs on a network, and try to edit them on a laptopm - especially if you are not hard-wired into the LAN.

Having said that, this CAN be done, but the price for this configuration is performance.

If there is ANY way you can have a local copy of the PBL on which to do your work, and then upload your changed PBL when you are finished with the task, then I'd strongly recommend that you use that option.


Olan