Nope, but i can shortly describe my solution.
I load the csv files with the stored inputfield values together with an unique key and concatenate the csv file with the field from the db I've declared as an inpufield (where not exists MyUniqueKey). This way, I have a Qv Table with the uniques keys and all the already stored inputfieldvalues together with the uniques keys not already have a stored inputfield value. At last, i declare the field as a inputfield.
In the gui i have a tablebox with the inputfield value and relevant other fields. On top of this tablebox i have a blank textbox (so the user can't use the built in inputfield function to write).
I have an button-triggered macro that only runs if the user has made a few selections (like narrow down the possible entries to one) and then starts up a few vbscript inputboxes where the user writes the values he want to append to the inputfield. By using inputboxes instead of the builtin inputfield function Im in better control of what the user is allowed to type and also have the possibility to add additional info like timestamp and OSUser.
Every time a user opens up the application, a macro runs that checks if a variable set in the load is the same as another single-value inputfield, it variable = inputfield = true, do nothing. If variable != inputfield I restore the inputfields and then put the same info as in the variable to the inputfield. This can sound a bit overkill, but i want the user to always see his own newly inserted inputfields and other users inputfields inserted before the last reload.
By using a variable and a single-value inputfield i take advantage of the principle that a inputfieldvalue survives an reload, a variable doesn't. So a variable is common for all users and inputfield isn't.
When the document reloads, i simply add +1 to the variable, and the next time a user logs on the variable will not be the same as the inputfield and the inputfields are restored (and showing the same as the csv file).
