It seems like folks love to hate the profile docs. Jake got the response he was hoping for ;-) But in my opinion profile docs are sometimes quite nice if used where appropriate and you know how they work.
I don't experience problems with caching of profile documents. - Probably because I have used them in a single client-type and single author situation only. It's when you start mixing either of these or updates on several servers concurrently you may get into trouble.
Although caching occurs in the front ends (notes client session and Http web server task), profile docs can be quite safely manipulated with backend lotusscript.
I have a simple db that I used for learning, demonstration and monitoring how updating and caching works for profile docs. (You can mail me for a copy.)
It seems like folks love to hate the profile docs. Jake got the response he was hoping for ;-) But in my opinion profile docs are sometimes quite nice if used where appropriate and you know how they work.
I don't experience problems with caching of profile documents. - Probably because I have used them in a single client-type and single author situation only. It's when you start mixing either of these or updates on several servers concurrently you may get into trouble.
Although caching occurs in the front ends (notes client session and Http web server task), profile docs can be quite safely manipulated with backend lotusscript.
I have a simple db that I used for learning, demonstration and monitoring how updating and caching works for profile docs. (You can mail me for a copy.)