Project Save As is Grayed Out!

[natasftw · Accepted solution]

So then, why open the project at all?  Just rename it from windows explorer.  If all you're trying to do is rename it, this is the easiest way.

[battler.]

Hm, actually I know that if ever I do that to a VI of the project it will break everything.  However, I hadn't thought about it for renaming a project.

Does anyone know if it's a good idea to rename the project file on disk?  I would also need to rename the LVLPS and ALIASES files?

[natasftw]

I've done it lots of times.

I'm thinking you don't understand what a project is.  A project is just links to the items it contains.  It doesn't actually contain anything.  That's why the project breaks if you change the name of the VI.  You've broken the link and now it has no idea where to find it.  As you likely have that VI used as a subVI elsewhere in the project, you also break any VI that had it as a subVI.

There's a world of difference between changing the name of a VI and changing the name of the project.  Just change the name of the project and open it.  Everything else takes care of itself.

[battler.]

Yes, I gathered what you were saying 🙂  I do know what a project file contains.   I've been bitten before for changing VI names on disk.

However, there must be a reason why Save As is grayed but I can't think of it and seems to be a bug.  There are also ALIASES and LVLPS files associated with the project, at least one of which I assume is a backup.

This is a very large and important project so need to be sure!  I will make a copy and try what you said.  I appreciate the suggestion. 

[battler.]

Changing the Project file name on disk creates no issues.

[natasftw]

I couldn't tell you why it was grayed out.  I'm not sure if it is intended behavior or a bug.  It's possible they grey it out to prevent you from believing you're copying the project and everything it contains elsewhere by using save as.  It's also possible it should be selectable so you can rename it.  I'd lean more towards the first option as there isn't really any benefit to a "save as"  Save as doesn't delete the original so it's not an effective renaming option.

I'm glad things worked for you.

[tst]

A couple of relevant points:

1. Renaming the project file is potentially a problem if you have other files referencing it (sometimes people include projects in other projects, for instance). Presumably that doesn't apply in your case.
2. The other two files are meant to be data which is relevant to the project, but only applies on your computer, which is why it's in separate files - you can configure your SCC system to ignore those file types. They do need to have the same name as the project, but they'll just be created automatically. You can read up on them in the LV help.

[anonamouse]

My instance of this problem turned out to be due to the project having confilcts that needed to be resolved.  I went through the conficts, pointed to the correct version of each problem .vi, saved the project and then was able to save as...

Reading the previous posts helped me by giving me the idea of what to look for.  Thanks to all previous posters.

[thomas.]

Hi,

sorry for bringing up this topic again, but I haven't been able to solve the problem with the given suggestions.

I have MakerHub-VIs (Linx - Arduino Uno) in my project. As soon as I delete that portion of code, the "save as" appears enabled again.

Any ideas on how to solve this? Unfortunately, deleting this part of the code is not possible!

Best regards,

Thomas

[beuvink]

For anyone still interested in this after a decade.. had the same. Was caused by a Vi (no longer in use) having a conflict in dependencies.

Vi itself didn't exist anymore but wasn't loaded or called as it was in a disabled case/piece of code

Removing the vi there solved the problem.

(And off-topic, but when you have this kind of Vi's you can't find them as there isn't a 'caller'. You might find them using 'why is this in dependencies')