Skip to main content
R
riverside341-Visitor
1-Visitor
December 20, 2014
Question

How to save file

  • December 20, 2014
  • 5 replies
  • 9544 views

Once again, I am battling Creo to do the simplest things anyone can do on a computer. I don't get it—did Creo developers make it a point to make simple tasks as complicated and counterintuitive as they could imagine?

All I need to do: to save an assembly file in a different folder. When I select Save As, a window opens for saving a file—but it doesn't let me save the file! I have no idea why this window even opens up. I can do complex tasks in every other program, except for Creo it seems, which saps me of patience and time for the simplest tasks anyone can possibly imagine.

Not a buyer, Creo. Not a buyer.

Update: Apparently, Creo doesn't like it when I try to save a file with the same name but in a different folder. "Save As" works as expected if I change the file name, but apparently Creo developers assumed that no one would ever want to save a file with the same name but in a different folder.


Why, that would just be of no use to anyone, I suppose. I would love to look at their design documents.


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

5 replies

T
TomD.inPDX17-Peridot
17-Peridot
December 20, 2014

That's because most software doesn't use "backup" any more.

What you were trying to do is known as a Backup copy in Creo terms.

D
dschenken1-Visitor
1-Visitor
December 20, 2014

That's because the surest way to make everyone miserable is to have multiple objects with the same name. Which one is the right one?

One project I was on had people making copies everywhere; like there were 12 copies of the same assembly in different folders and each person could be working on their own version, but come time to put them into the next level of assembly, which one is the 'right' one? Many of them were just making 'temp' versions to check things out and were in folders named 'temp_something' or 'test_something', but not all of them. And the latest version or the most recent version weren't necessarily the 'right' version. Oh, what a mess.

If you need a copy in another folder, Windows does that and does it well.

If you need to make a backup to save a version in case things go badly, Creo has Backup.

R
riverside341-VisitorAuthor
1-Visitor
December 20, 2014

David—the appropriate file name is for you and your team to determine. If naming different versions of the same file is a problem, you can establish a process whereby members in your team use different names. No need for software to impose its assumptions of what is proper on everybody—especially when those assumptions are not right all the time.

I tell you, I have rarely been this frustrated at software. Usability matters too. I am okay with spending an hour figuring out how to do something complex. But spending an hour figuring out how do simple things like saving a file, just because PTC devel thought it was cute to reinvent the wheel and completely change how "Save As" works?

No, thanks. Whatever advantages such features might have, they don't trump the costs—namely the lower usability of the software.

Why not dedicate devel resources toward tangibly improving what the software does instead of taking simple features that work well and make them so complex that suddenly one needs a course to use them again?

P
ptc-68120951-Visitor
1-Visitor
December 20, 2014

waw it is very nice thanks

R
rohit_rajan15-Moonstone
15-Moonstone
December 20, 2014

save as backup" in a different folder without changing name" is very much there in creo . and i have been doing that for years now...did i miss something?

R
riverside341-VisitorAuthor
1-Visitor
December 20, 2014

Look. People might well want to save a file in a different folder while using the same name *without* intending the new file to be a backup. It's a usability issue is all. I can save files in a blink of an eye, using any name I want, in any folder I want, in any other application. In SolidWorks, Adobe Illustrator, Photoshop, MATLAB, you name it.

But you come to Creo, and suddendly it's a science. You can save a file in a different folder using "Save As", but not with the same name. Or, it seems, you can use some "save as backup" option to save the file elsewhere using the same name—though if your motive is not to create a backup file, then you are likely to not even notice that option.

I would rather stare at the blinding sun for 60 seconds than have to use Creo on a daily basis for work. I don't care how long these misguided options have been around—they are still misguided.

R
rohit_rajan15-Moonstone
15-Moonstone
December 20, 2014

so i want to save a assembly file with the same name but in a different folder..so what changes? and if they both have the same name..so one is going to be backup right?

N
nhanratty1-Visitor
1-Visitor
December 20, 2014

Few suggestions for you...

1. Get a job in which you don't have to use Creo

2. Go on a training course and learn how to use Creo

but whatever one you choose please stop complaining!

Thousands of users over many years have produced fantastic products in Pro/Engineer and Creo without the need to tell the rest of the world how much they dislike it.

    R
    rohit_rajan15-Moonstone
    15-Moonstone
    December 20, 2014

    rightly said....

    i have issues with creo 2.0 the detailing area (symbols creation etc...)..but the point is its a nice and powerful software...

    solidworks...is very easy to use...but they are still putting in options..which have been there in creo/proe since ages...

    i have been using solidworks for 3+ years now....and creo for 7 years now...

    Terms & ConditionsAccessibility statement