As we have already talked about this here : Thread73-711544, I would like to know if you want an automatic fill of the form list.
In other words, are you thinking of creating a function that gathers all forms of a certain name format and displaying that ?
In which case I would say it is impossible.
Otherwise, I do not understand why our previous solution does not interest you. Have you tried and did it work ?

Pascal.

To clarify, there are 3 forms that the user can use to create documents.  What I would like is when the user clicks on New Document, it prompts them with a choice of the 3 forms and depending on what is displayed in the view, determines what is populated on the document they choose.  

It's like having 3 fields that are exactly the same on 3 different forms/docs.  But depending on what else is needed to finish a document, determines what form to choose from the list under the New Document button.  

I have a feeling this may not be possible, but I'm just checking.  I appreciate all the help.

You cannot create a new document depending on a view. That is too vague and unspecific, aside from the fact that a Notes document can only inherit from a single document : the one that is selected when creating a new one.
If you have anything more complicated than single-document inheritance on creation, then you need to script it in the PostOpen event.
On the other hand, inheriting information depends entirely on the form you use, so you could use the suggestion I have already given, create three different forms and have each one inherit differently from the selected document.
But if you need multiple-document inheritance, then we are no longer talking inheritance but PostOpen script and @dblookup functions in header fields and other such info-gathering means.

Pascal.

That last piece of advice is probably what I'll have to look into.  How difficult are @dblookup functions?  And what/where would be the easiest way to become familiar with them?  

For a better idea of my database, I have a 3 stage database.  It begins with basic data entry (names, dates, corresponding information).  Then another user will be prompted and they will finish out the other pieces based on that data.  The third step depends on the completion and accuracy of the first 2 before a report can be printed.

@Db functions are quite easy, and the Designer Help db is well written on that subject. Review the articles in the Help and you should have everything you need.
The difficulty lies not in the retrieval of information, but in what you do with it afterwards. A @DbColumn retrieves multiple values, which you then have to manage and eventually break down according to what your needs are. That can prove tricky, especially if you recover info from multiple sources.

Pascal.