Can't really say why it doesn't work for you. This is how it is supposed to work and it has been this way for a long time. I can't tell from your post exactly what the problem is you are having. Is it one of these:
- The app you are choosing is grayed out and unable to be selected. This indicates the application can't open that type of file. An example would be trying to open a text document with the OS X Calendar app. Can't be done.
- Or is the problem that you are able to select an application but it keeps reverting back?
- Or is it that you selected an application, Get Info shows it as the one to use, but it still opens in a different application?
I don't know if it was lack of precision in your wording but isn't OpenOffice a suite of applications? I don't have OpenOffice so I may be incorrect here but did you mean you cannot set it to open in OpenOffice's Calc application? Or is "OpenOffice" a central point from which OpenOffice compatible documents are opened?
Its number 2: It keeps returning back, or basic not assigning the selected program at all.
Yes: Open Office is a central point (like the MS office i guess) from which compatible documents are opened.
Yep - it is very strange and kind a new situation for me. Use to work allright but not for the last 4 month.
I can't seem to find a post with a solution to this problem. I guess I'm not figuring out the correct search term(s) to use.
Could be launch services is corrupt and needs to be rebuilt. The usual symptom is double entries in the right context "open with" menu, not the inability to change the default application, but it might be it. Open the Terminal application and copy/paste one of the following commands into it and hit return. I think the first one is the one you want; the second may be for Lion/Mtn Lion.
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.fram ework/Support/lsregister -kill -r -domain local -domain system -domain user
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user
You might also try repairing permissions in Disk Utility