Sharepoint Workbook reversion to earlier version due to Internet link broken VBA

waygar 

Unfortunately, directly monitoring and forcibly closing Excel due to disconnections in a co-authored workbook isn't feasible using VBA solely because of security restrictions and limitations in controlling external processes. However, there are alternative approaches you can consider to mitigate the reversion issue:

1. Leverage Sharepoint Versioning:

• Sharepoint automatically versions uploaded documents. Configure version history to keep a sufficient number of versions (e.g., past hour, daily).
• If a reversion occurs, manually restore the latest version.

2. Implement a "Check-In/Check-Out" System:

• Designate one person as the responsible editor at a time.
• Use a manual system (e.g., shared document) to track who's editing.
• The current editor checks out the workbook, preventing others from modifying it simultaneously.
• Upon completion, the editor checks in the workbook, making it available for others.

3. Explore Third-Party Solutions:

• Consider tools like Docupace or CoGuard that offer greater control over co-authoring, access, and conflict resolution in Excel workbooks stored on Sharepoint.

4. Improve Network Connectivity:

• Investigate potential network issues causing disconnections (e.g., VPN stability, individual internet providers).
• Implement better connection solutions to minimize disruptions.

5. Educate Users:

• Train users to save the workbook manually before VPN timeouts or disconnects.
• Emphasize the importance of closing the workbook properly when connectivity issues arise.

While a perfect solution might not exist due to inherent co-authoring limitations, these strategies can help you reduce the frequency and impact of workbook reversions. You can choose the approach that best suits your group's workflow and technical capabilities.