DWG history w/ path?

[Anonymous]

Is there anyway to get a list of recently opened files with paths?
Currently I've got a list of 9 recent files but just the name. This does me
no good as we name Tentative Maps "TM" and Improvement Plans "IMP" and so
on. These files are in proejct folders that have a unique name related to
our project numbering system.

Maybe I need to buy a add-on app. Any advise?

Thanks
EC

[Anonymous]

Ed Canvasser wrote:

> Is there anyway to get a list of recently opened files with paths?

Take a look at RECENT.ZIP in the Free Stuff section of
http://www.dotsoft.com. It shows the last 26 files on a menu, as you
hover over an item on the menu it shows the full path below the command
line.

Terry

[Anonymous]

So for Project 12345 you have a file named "TM.dwg" and then for Project
45678 you have another file named "TM.dwg"?? Scared o' that!
Having multiple files with the same name on the same network is a dangerous
game...

Just as an FYI, we have a code for all our projects that goes like this:
YYLPP where YY= the year (2006 = 06), L= Location (0=Home office),
PP=project number (01=the first project of the year). So 06001 = the first
project of 2006 assigned to the home office. Then for file naming, we use a
shortened code of s06XX123.dwg where "s" is the file code for the year
(s=2006), XX= file type (af=architectural floor plan), and 123 = the drawing
number or building level (001 = the first drawing in the series). So
s01af001.dwg = the 1st floor arch floor plan for the first project in 2006.
It sounds complicated, but it's pretty simple. AND it protects us from
accidentally overwriting files from different projects.


"Ed Canvasser" wrote in message
news:5039091@discussion.autodesk.com...
Is there anyway to get a list of recently opened files with paths?
Currently I've got a list of 9 recent files but just the name. This does me
no good as we name Tentative Maps "TM" and Improvement Plans "IMP" and so
on. These files are in proejct folders that have a unique name related to
our project numbering system.

Maybe I need to buy a add-on app. Any advise?

Thanks
EC

[Anonymous]

Not getting full path under the command line. Any suggestions?

[Anonymous]

That's a more in depth approach to what we do but I was also going to
suggest coding the job # and phase into the file name.
When I came here the server was littered with literally thousand's of P2
drawings!

[Anonymous]

ecanvasser wrote:

> Not getting full path under the command line. Any suggestions?

I had remembered to add that but forgot to change the download zip.

I'll change the build in about an hour.

Terry

[Anonymous]

Terry W. Dotson wrote:

> I'll change the build in about an hour.

Changed.

Terry

[Anonymous]

Thanks so much, that did the trick!

[Anonymous]

On Thu, 15 Dec 2005 19:06:59 +0000, pkirill wrote:

>So for Project 12345 you have a file named "TM.dwg" and then for Project
>45678 you have another file named "TM.dwg"?? Scared o' that!
>Having multiple files with the same name on the same network is a dangerous
>game...

No it isn't, if your users are grownups. It actually has many benefits.

Matt
mstachoni@comcast.net
mstachoni@bhhtait.com

[Anonymous]

But Matt, with all your experience, are the users always adults?

[Anonymous]

We've been doing it this way for +/- 17 yrs. and I can't remember ever having any major issues. I can see how someone could loose a file, but I can honestly say we've been fine w/ our very simple approach.

Thanks for the input, it's nice to share our techniques and procedures. However, the problem that I see with all the info in the file name is compliance. For instance who's insuring that the files are being named in compliance w/ company std's? If your not on top of it, seems like it could get out of hand fast.

Our file names are either simple abbreviations (2 to 3 letters) or we tend to spell out a somewhat literal name for unique files (ie TM - Save.dwg... or Concept1.dwg, etc.). Works for us and I'm glad it does.

Thanks for the input and suggestion for RECENT app. Works just fine.

[Anonymous]

>For instance who's insuring that the files are being named in compliance w/
>company std's?

Not a problem if your user's are grown ups. Plus we have tools that ease the
creation of new files that name files according to the standards. And the
best form of compliance checking we have is peer-to-peer, then next is that
much of our automation relies on it. I'm a big supporter of "if it ain't
broke, don't fix it" - so if works for you, keep doing it. But your original
post points out one of the biggest issues. I don't know what kind of work
you do, but often we use data from previous projects and if I had two
ABC.dwg files open and they were remarkably similar, I could see getting my
data mixed up and never really knowing the difference.


wrote in message news:5040135@discussion.autodesk.com...
We've been doing it this way for +/- 17 yrs. and I can't remember ever
having any major issues. I can see how someone could loose a file, but I
can honestly say we've been fine w/ our very simple approach.

Thanks for the input, it's nice to share our techniques and procedures.
However, the problem that I see with all the info in the file name is
compliance. For instance who's insuring that the files are being named in
compliance w/ company std's? If your not on top of it, seems like it could
get out of hand fast.

Our file names are either simple abbreviations (2 to 3 letters) or we tend
to spell out a somewhat literal name for unique files (ie TM - Save.dwg...
or Concept1.dwg, etc.). Works for us and I'm glad it does.

Thanks for the input and suggestion for RECENT app. Works just fine.

[Anonymous]

I don't remember the name of the software as it was a long time ago. I think
is was Drawing Librarian and it was a fast DOS file viewer that could
overlay two files on top of one another making it possible to visually
determine what was different.

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/


"pkirill" wrote in message
news:5040342@discussion.autodesk.com...
>For instance who's insuring that the files are being named in compliance w/
>company std's?

Not a problem if your user's are grown ups. Plus we have tools that ease the
creation of new files that name files according to the standards. And the
best form of compliance checking we have is peer-to-peer, then next is that
much of our automation relies on it. I'm a big supporter of "if it ain't
broke, don't fix it" - so if works for you, keep doing it. But your original
post points out one of the biggest issues. I don't know what kind of work
you do, but often we use data from previous projects and if I had two
ABC.dwg files open and they were remarkably similar, I could see getting my
data mixed up and never really knowing the difference.


wrote in message news:5040135@discussion.autodesk.com...
We've been doing it this way for +/- 17 yrs. and I can't remember ever
having any major issues. I can see how someone could loose a file, but I
can honestly say we've been fine w/ our very simple approach.

Thanks for the input, it's nice to share our techniques and procedures.
However, the problem that I see with all the info in the file name is
compliance. For instance who's insuring that the files are being named in
compliance w/ company std's? If your not on top of it, seems like it could
get out of hand fast.

Our file names are either simple abbreviations (2 to 3 letters) or we tend
to spell out a somewhat literal name for unique files (ie TM - Save.dwg...
or Concept1.dwg, etc.). Works for us and I'm glad it does.

Thanks for the input and suggestion for RECENT app. Works just fine.

[Anonymous]

On Fri, 16 Dec 2005 16:11:49 +0000, Matt
wrote:

>But Matt, with all your experience, are the users always adults?

Well, no. That has yet to happen.

Matt
mstachoni@comcast.net
mstachoni@bhhtait.com