My new pet peeve - final

[devenv exe]

At my current work place, we have databases named like below on the same instance of SQL Server 1. Database1 2. Database1 New 3. Database1 Current 4. Database1 Recent 5. Database1 Latest 6. Database1 Real For some reason, no one wants to delete any of them.

"Coming soon"

[Lost User]

Almost as bad as putting "new" to indicate that this is a new version.

[chriselst]

We have live servers with new at the front of the name. I hate to think what we'll have if they need replacing again.

Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.

[W Balboos GHB]

No version control problems - give them a Wiki. Let them fight it out amongst themselves.

"The difference between genius and stupidity is that genius has its limits." - Albert Einstein

"As far as we know, our computer has never had an undetected error." - Weisert

"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010

[S Houghtelin]

Reminds me off all those Cher FINAL TOUR! tours.

It was broke, so I fixed it.

[Kschuler]

The one with the most recent maintenance date.

[CPallini]

Same here, with 'latest'.

THESE PEOPLE REALLY BOTHER ME!! How can they know what you should do without knowing what you want done?!?! -- C++ FQA Lite

[Nish Nishant]

The one with the most recent last modified date?

Regards, Nish

---

Latest article: Using the Microsoft Azure Storage Client Library for C++ Blog: voidnish.wordpress.com

[JimmyRopes]

If more than one person will be working on the document simultaneously then source control (like SVN) is the best option. For documents you are working on that others are not contributing to try the following naming convention. It works for me. document20140103.docx document20140131.docx document20140206.docx document20140223.docx document20140316.docx You will always know the latest and greatest version of the document. Well at least the latest version. :cool:

**_Once you lose your pride the rest is easy.

I would agree with you but then we both would be wrong._**
The report of my death was an exaggeration - Mark Twain Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am. JimmyRopes

[Chris Maunder]

You'd think. Except it isn't. You've had merge conflicts before, right? Same deal.

cheers Chris Maunder

[Ennis Ray Lynch Jr]

Recently while sitting in at the end of a share point configuration provided by a vendor I noticed several copies of an SSRS report in the share. I asked what didn't you enable versioning? The attendees on my side looked perplexed and the "consultant" said, "Yes, I suppose we could have done that. You just can't win!

Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost "All users always want Excel" --Ennis Lynch

[Nish Nishant]

Yeah, that sucks then :-)

Regards, Nish

---

Latest article: Using the Microsoft Azure Storage Client Library for C++ Blog: voidnish.wordpress.com

[Jeremy Falcon]

Chris Maunder wrote:

This is why documents need source control...

You ever try a combo of your code repo and the built-in revisioning tools in Word? Da Link[^]

Jeremy Falcon

[Lost User]

Release your inner demon. ..take a copy of "document - final - DG-comments.docx", copy it once in the directory it's already in, and add the remark "probably the current latest version".

Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

[Ravi Bhavnani]

My solution to this common problem is to rename older versions of the document, e.g:

• Document.docx The latest version of the document.
• Document - 01.docx First edit.
• Document - 02 - Updates per Joe Updates made in response to Joe's review.
• Document - Draft An unsequenced draft version of the document.

Chris Maunder wrote:

This is why documents need source control...

Of course they do!  As does any edited collateral.  Aside: File versioning came standard with my first OS (VAX/VMS, circa 1980). :) /ravi

My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

[Mycroft Holmes]

I make them put their initial after the database version, then I know who the owner is. I'm also in the habit of taking DB off line on the dev and UAT servers, if no one screams in a month I can delete them.

Never underestimate the power of human stupidity RAH

[Roger Wright]

That's why we have date stamps, Chris! ;P

Will Rogers never met me.

[R Erasmus]

Suggestion: Don't put the word final in the name, put it in the doc itself. That is how we do it in any case... Why you may wonder... You'll have too many docs to maintain/store which becomes ugly. (As you have seen with the names issue) I the case of using a versioning tool you end up with multiple (and in actual fact this can extend to 100s) of different documents which should only be one document with different revisions... One being internally marked as draft, the next revision being internally marked as final. The draft would usually go through review, update and verify process. The final will never contain comments. THUS: One doc with same name and mechanism to indicate state of document internally, managed through source/revision control system or something similar.

"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>

[Kiriander]

Sort by write date, theone with the last date is the last one. Problem solved.

[Member 4724084]

At the risk of starting a war, why not just check the last modified file property? Free versioning that comes with every platform.