I've just create a preference sheet for all projects, and uploaded it. The results was that none of my computers was receiving new jobs.

Having a look at my project's preference, I found any field were empty.

The explanation, as far as I know, was that my preference name was named "new [date]"

What I'm thinking is :
1/ As long as only 4 names are usefull, and changing a name is impossible, a combo box with the possible name would be better
2/ Deleting every settings when no correctly defined preference are defined is a bad behaviour, doing nothing in this case is the right answer. And giving a message to highlight a problem a better answer
3/ Having the ability to save settings directly in the edited prefs would be nice

I saw a similar behavior although I got the names right :-) I had no preferences in BAM so I first added "school" as a non-default preference. It saved and propagated just fine. My Global preferences were wiped out however.

No big deal. I created a "home" preference as a default and all seems well, but this is undesirable behavior. The saved "home" as default doesn't show up as "home" though. It is only the Global default. This may be the desired behavior(?), but it wasn't obvious to me that this would happen until it did.

A pull down menu for acceptable names would be nice. I guess there could be an entry for "other" for future growth.

We hope that the BOINC Manager will soon support prefs per host with custom names. So I think there is no need for a combobox for the prefs for now

My problem was entering valid names and having bad things happen. I'm guessing this is just a variation of Bronco's problem. Deleting existing venues that weren't specified in the request is not a good thing. It may only be a user education problem, but there seems to be a problem somewhere.

Specific host venues with custom names would be nice, but as you say it is a BOINC issue. If it's six months (or so) away then a pull down box might make life easier for all. Think of all the questions!

There is no problem with custom names, the only problem here is the lack of a default preference.

I'll make a fix for this a.s.a.p.

There is now a warning on the preference page when the default preference is missing.

In addition, when a new preference is created, and there is no default preference yet, the newly created pref will become the default one.

Thanks for this fast solution

A good fix. Now keep me from doing stupid things