I'm using the code listed here:
http://msdn.microsoft.com/en-us/library/ms553069.aspx
With an additional line added as a call to .update() after the property is set in order to save the changes, but even with a weight of 10,000 the search results for my property are still at the bottom, particularly below title. Is there some other things that need to be done in order to get the weighting to propogate?
I've also tried setting the title, author, and filename to 0, setting the property (keywords) to 9999, and setting length normalization of the property to 0. The results shift a bit, but searches with keywords that match the property still do not match.
All tests were done with a full crawl afterwards, reset IIS, and recycle the shared services app pool.
I can give you any extra information you might request.
Thanks, Stefan
UPDATE (6-19-09): Added a bounty of 500 to this. Very little information about this feature available online, apparently a good answer would a huge service to the internet community. It'd probably save me a week too :)
UPDATE 2 (6-19-09): The schema is essentially this: OOB sharepoint document content type with added text field "Keywords". Managed property attached to ows_keywords(Text).
UPDATE 3 (6-19-09): Sharepoint Search Bench from Codeplex has helped the search a lot.
UPDATE 4 (6-19-09): I've arrived at a solution that involves creating many (5 right now) more managed properties with the same crawled property. Each weight is set to something unusual (like 9999). These do enough to buoy the keyword results to the top. Less than ideal though. Still looking for a solution.
The solution in Update 4 is what I ended up with. As Lars commented, the search is not very flexible and despite offering tweaks to the property weightings, the effect is not always what you would expect.