Community
Inventor Forum
Welcome to Autodesk’s Inventor Forums. Share your knowledge, ask questions, and explore popular Inventor topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Too many Periods in filenames

8 REPLIES 8
Reply
Message 1 of 9
Anonymous
529 Views, 8 Replies

Too many Periods in filenames

It seems Inventor 8 in certain circumstances does not like more than 2 periods
in a filename in addition to the period before the extension. I have a part in
assembly named 6.350 I.D. LINER BUSHING.ipt and if I edit it to do a save
copy as, IV asks me to select a translator. If I eliminate one of the periods in
the filename, it does not complain.

I checked using the SaveCopyNReplace macro and that works OK, but Autodesk
needs to look at this issue with their Save Copy As command.
8 REPLIES 8
Message 2 of 9
Anonymous
in reply to: Anonymous

you know, i JUST started using periods in some of my filenames. still
hanging on to those DOS days i guess. if i were you i'd dump the periods for
your ID and just leave the one for your number. also, you can always use -
or _ in substitution. don't know if you do any programming, but i do and
sometimes those pesky periods give me all kinds of problems.

--
Mark A. Bystry
Engineer
Ziggity Systems, Inc.

Dell Precision 420 Workstation
Dual 933 MHz Pentium III
WinXP Pro SP1
768 MB RDRAM
PNY Quadro4 750 XGL
nVidia 6.14.10.5214
Message 3 of 9
Anonymous
in reply to: Anonymous

I had this happen to me a couple months ago. I inadvertently did a "save
copy as" filename..ipt and for the life of me I couldn't figure out what was
going on. Then I just happened to see the double dots.

I generally use the underscore for the dots in a filename: 6_350 ID Liner
Bushing.ipt.

"Bob" wrote in message
news:6F7FADBE785F8B9802DF5A947259DD8C@in.WebX.maYIadrTaRb...
| It seems Inventor 8 in certain circumstances does not like more than 2
periods
| in a filename in addition to the period before the extension. I have a
part in
| assembly named 6.350 I.D. LINER BUSHING.ipt and if I edit it to do a save
| copy as, IV asks me to select a translator. If I eliminate one of the
periods in
| the filename, it does not complain.
|
| I checked using the SaveCopyNReplace macro and that works OK, but Autodesk
| needs to look at this issue with their Save Copy As command.
|
|


----------------------------------------------------------------------------
----
Message 4 of 9
Anonymous
in reply to: Anonymous

But citing "Ease of Use", since IV makes the Part name property the Same as the
Filename (minus the extension) AND I use that property in my Parts List,
using _'s in place of .'s is not very effective as then you have to edit the parts
list and freeze all the items you changed. Or does IV have some automatic
method of substituting these characters in the parts list that I am not aware of.

And at least if they are going to be consistent, then they need to either fix this
one area or cripple the rest of IV to also not work with files not meeting the
correct criteria.

Bob


"Ron Crain" wrote in message news:FCD0C699DEBA4563C8CBDE20BC851398@in.WebX.maYIadrTaRb...
> I had this happen to me a couple months ago. I inadvertently did a "save
> copy as" filename..ipt and for the life of me I couldn't figure out what was
> going on. Then I just happened to see the double dots.
>
> I generally use the underscore for the dots in a filename: 6_350 ID Liner
> Bushing.ipt.
>
> "Bob" wrote in message
> news:6F7FADBE785F8B9802DF5A947259DD8C@in.WebX.maYIadrTaRb...
> | It seems Inventor 8 in certain circumstances does not like more than 2
> periods
> | in a filename in addition to the period before the extension. I have a
> part in
> | assembly named 6.350 I.D. LINER BUSHING.ipt and if I edit it to do a save
> | copy as, IV asks me to select a translator. If I eliminate one of the
> periods in
> | the filename, it does not complain.
> |
> | I checked using the SaveCopyNReplace macro and that works OK, but Autodesk
> | needs to look at this issue with their Save Copy As command.
> |
> |
>
>
> ----------------------------------------------------------------------------
> ----
>
>
>
>
>
Message 5 of 9
xavierl
in reply to: Anonymous

probably a windows issue. there is a list of things not to put in a filename ie . ( ) .{}

I had this same thing in another program. the problem is its not consistent, so avoid at all costs.

I believe a lot of programmers still use the 8.3 format just to be shure.

Frans X Liebenberg
Message 6 of 9
Anonymous
in reply to: Anonymous

Hi Bob
You May want to be carful naming files like this. I have had 2 issues with a discriptive file name in the past; first you will probobly duplicate that name in the future, or something very close to it, second when sharing inforamtion with contractors I have had trobles copying files to CD that have file names more then 68 charactors in legnth. Your best bet is to use dumb old sequential numbering.
Mike
Message 7 of 9
Anonymous
in reply to: Anonymous

I've always edited the partnumber field.

"Bob" wrote in message
news:C18BA3D7E75EDC6D22476E2005D4B682@in.WebX.maYIadrTaRb...
| But citing "Ease of Use", since IV makes the Part name property the Same
as the
| Filename (minus the extension) AND I use that property in my Parts List,
| using _'s in place of .'s is not very effective as then you have to edit
the parts
| list and freeze all the items you changed. Or does IV have some automatic
| method of substituting these characters in the parts list that I am not
aware of.
|
| And at least if they are going to be consistent, then they need to either
fix this
| one area or cripple the rest of IV to also not work with files not meeting
the
| correct criteria.
|
| Bob
Message 8 of 9
Anonymous
in reply to: Anonymous

First, I never have a filename longer than what
will fit on one line of my parts list.

(Maybe about 40-50 characters tops)

 

Second, I am more likely to duplicate a file name
using dumb old sequential

naming (I assume you are talking about DOS 8.3
convention).

 

Third, With proper project management I do not have
to worry about duplicate names.

 

4th, never had problems using paranthesises in
Filenames. Windows will not allow

the following characters: / \ : * ? " <
> |

You can however fake double quotes by using 2
single quotes.

 

5th, most of our customers do not have Inventor,
and I have to make MDT files for

them, usually using a combination of step and DWG
export. The part names in

this case are a none issue and makes easy reading
of MDT's browser pane.

 

Lastly (for now), proper Windows programming should
make this a NON ISSUE

(I have done my own share of programming in the
past). It's not like AutoDesk

has to support anything other than Windows (though
most of us wish they would)

DOS is dead, the future is now!, etc,
etc.

 

Finally (I know, lastly was last, long day), I'd
like to hear Autodesk's take on all this

naming convention stuff.

 

Bob S.


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
Hi
Bob
You May want to be carful naming files like this. I have had 2 issues
with a discriptive file name in the past; first you will probobly duplicate
that name in the future, or something very close to it, second when sharing
inforamtion with contractors I have had trobles copying files to CD that have
file names more then 68 charactors in legnth. Your best bet is to use dumb old
sequential numbering.
Mike
Message 9 of 9
Anonymous
in reply to: Anonymous

THE best way to put files on a CD is to use WinZip (not Windows built in
zip folders). Zipping the files (with WinZip) not only makes the saved
files smaller but also preserves the file attributes and the longer
filenames. If you burn files to a CD, they end up being ReadOnly when
you copy them off. If you have file names that are really long, you can
hide those long names by putting them in a zip file.

Now, the reason you DO NOT want to use the Microsoft Zip Folders; it
doesn't recognize all the files in a zip. We have had several cases
where we zipped up an assembly, put it on CD or email it and at the
other end, the recipient complained that files were missing. If they
run WinZip to extract the files, they get all the files contained in the
zip.

MikeQ wrote:

> Hi Bob
> You May want to be carful naming files like this. I have had 2 issues
> with a discriptive file name in the past; first you will probobly
> duplicate that name in the future, or something very close to it,
> second when sharing inforamtion with contractors I have had trobles
> copying files to CD that have file names more then 68 charactors in
> legnth. Your best bet is to use dumb old sequential numbering.
> Mike

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report