I really don't have a great recommendation on how to handle this other than build some automated system that tracks the current build number on a daily basis, perhaps even putting it in each database.
Put it in the database? :laugh: You mean the one we CAN'T restore?
How about a central database to store all your version data and history? If you want to make it independent of SQL Server version issues try MySQL. Or :shudder: Access. Excel does not have any version problems. :Whistling: Maybe a Text file. Wait, there's all that UTF-8 and Unicode business. I know! PUNCH CARDS! Where are those 15 dozen boxes of blanks? Ahh, back of the car for weight in the snow. Everything is good for something.
Side bar: Why did they think the stand up comedian committed suicide? He killed himself.
Seriously though, reading legacy formats is, and likely always will be, a challenge. Just the other day a legacy application that has been running flawlessly for years went belly up. It threw errors talking about "linked tables". The guy working the issue asked me, "What the heck are linked tables?" The client had to dig to find the Access CD and actually install it on the machine in question. Access pointed to two different MySQL databases and some tables on the AS-400. One of the MySQL tables was corrupt and needed a table repair.
ATBCharles Kincaid