which of the examples did you try which I said.the one that ends in xml or ones that end with html.The ones that end with html is what is referred as "unsafe lookups" which is basically like a text box in a html page where you type "select * from mytable" all the connection params are in the form itself for everybody to see so it is considered unsafe.In the safer forms(xml example) basically the connection info is encapsulated within the server,so you basically create connection info in livelink admin pages under webform data connection,but you can still pass valid queries.What you really want to know is when you hit tab then you are executing a livelink request handler probably webform.datalookup or something of that sort.Now the result set is given to you in the javascript object.for debugging you want to make the vanishing javascript window that posts to your form visible so you can understand the flow.Now if your real form template is posting to a table and if middlename is a field in your table you should be able to follow the OT example and write your own stuff.I don't think you need other than javascript anything else.
See these in the file Example_template.html
// This example assumes that the current LES server has five things:
// A database connection object that points to the current LES database.
// A database lookup object named ExampleLookup1 whose SQL statement to
// execute is:
// select FirstName, LastName, MailAddress, GroupID from KUAF where Name=:A1
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010