[xpost from google livecycle group]:
So I'm revisiting the art of pre-populating a form. You know, the concept that is really trivial in most applications except livecycle....
[exit jab mode 
]
In three internet posts/examples that I saw, each had the render service tied specifically to "the form" that is being pre-populated. Kind of makes sense, because you have to poke the data into the specific form, right?
But that has me thinking that now the render service can no longer be used across multiple forms because you have to reference "the form" to poke the data into the form's field. Now it appears that each form will require its own render service in order to prepop.
Am I understanding that correctly? If I am, what is the impact on performance if each form needs its own render?
At this point I'm thinking that writing a short-lived custom component using the LDAP api's and populating the form upon form initialization might be a preferrable approach.
Here are the sites I researched:
Roland Lopez: http://www.roland-lopez.com/tech/
Seth Riley: http://livecycleapps.wordpress.com/2009/01/29/prepopulate-form-for-dis play-in-workspace-and-route-it-to-another-user/
ES Lifeline: http://eslifeline.files.wordpress.com/2008/05/renderservicefinal.pdf
Sing me,
All rendered out,
Elaine