Peter,
@Kirk: Oh wow, OK, that is a bug. Platform is WindowsXP BTW. I'll wait for a fix in a future release if it gives me more grief.
I have a fix in the works. The Keywords field is complicated by the fact that it is a 'repeating field' and is treated specially. What you're pasting into the Keywords field is entirely legal, but because it has no repeating field separators (either ';' or ',' which depends on a Preferences setting), everything you've entered is likely going to be treated as one really
large keyword, which will likely not work well in searching situations. If you want to have a big blob of values all strung together, I'd suggest using one of the non-repeating fields that have some room in them like Caption, Headline, or Special Instructions. Otherwise I suggest separating out your variables with field separators like so:
Model: {modl}, Lens: {lenstype}, Metering mode: {meteringmode}, Exp. Comp.: {comp}, ..., {comment}, {software}
Notice the use of ',' between keywords. Note: I omitted some of your text to keep things brief.
At any rate, even the above suggestion won't work until my fix is released in the next update. But once it does get released, you could do the above, and then Keyword searches on a database would match 'Model: D200' or 'Nikon Capture NX2', etc. This will make it more useful than searching for one really large string that you don't know the entire contents of. In the end it will really just matter what kind of search engine your database uses and if it allows substring matching then you could go ahead and keep your Keywords as one really large blob anyway. If the search engine only allows exact matches then splitting up your Keywords will be imperative for good results.
HTH,
-Kirk