Some disappointments are familiar to every Excel user. You or your colleagues may enter incorrect values or even delete critical data by mistake.

MS Excel Track Changes feature comes with limitations: history of changes is periodically deleted, it does not do backups and works only for shared workbooks. Hello David, XLTools Version Control provides a different functionality compared to native Excel track changes. You can view the history of all saved versions (when and who made the changes, comments to these versions). You can compare two versions of a sheet at a time – Version Control will pull these two versions, mark them ‘Newer’ and ‘Older’, and it will highlight the cells in the Newer version that are different compared to the Older. You are most welcome to download XLTools and activate the free trial – it will take a few minutes and you can see if XLTools can be helpful with your tasks. Hi, I’m interested in using this for version control.

Excel

Wine barrel decor. Does it allow distributed revision control?Our use case is 2-3 developers working on a spreadsheet made up of several pages. Often the spreadsheet is opened from it’s location on a shared network drive, minor changes made and sometimes the version number is not incremented.This makes it very hard to track changes and also who made them.

Here's an alternative. Missing iso 9660 image. Import pandas as pd def convertexceltime(exceltime): ' converts excel float format to pandas datetime object round to '1min' with.dt.round('1min') to correct floating point conversion innaccuracy ' return pd.todatetime('1899-12-30') + pd.totimedelta(exceltime,'D') thanks.

Git

Ideally we would pull the spreadsheet to a working directory, do a diff and commit changes then push them to a master repository. Would it be suitable for this kind of workflow? Would like to see an answer to this question.

Distributed is what’s really needed in a case I am considering as well. Have many people working on one spreadsheet and need to have commits with users’ name and comments. Features like working copies, a central check-in site, and conflict management/resolution would be the best.A work-around might be to have users log into the same remote machine, work on the single-copy worksheet there (one at a time), and then commit changes.

Would that be a license violation?