Compare the database footprint with library footprint -Skill

Has anybody seen inconsistent results with fileTimeModified()?

Using timeToString(fileTimeModified(axlOSSlash(<valid path to PSM file>))) I see some results match between all computers and some have an off-by-one-hour issue. I suspect it's due to daylight savings time here in the US, but I can't figure it out. The actual file save date is correctly returned on some PCs for a file saved in August, and on others the returned value is one _exactly_ one hour later.

It turns out that the different is 17.2 vs 17.4. 17.4 appears to have fixed the issue. However, Cadence no longer provides a list of functions that were changed (or added or new) with each Allegro version and they tell me there's no change, no it's a mystery. Certainly the support answer of no change does not reconcile with my experience running the functions on the same PC and getting different results under 17.2 and 17.4...

HI Is it possible to share this code at all, Thanks

If cadence could come up with a utility to find differences in footprints it would be much helpful to PCB designers since the updates could happen often sometimes. There was an earlier post too that requested a solution for the same question.

We use a text field and property to manage the version of the symbol. Using Skill you can easily compare the version of the symbol placed in a design to what is currently in the library. 

Using Dal Tools also provides a much more detailed list of what the differences are, which can sometimes be too much detail to what you're actually looking for.