Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

R5 - In a view, creating a feature to open a list of forms

R5 - In a view, creating a feature to open a list of forms

R5 - In a view, creating a feature to open a list of forms

I asked a similar question a while ago, but I think I know now exactly what I'm looking for.  Using an action button, create some type of pompt for the user to select the document that will display the data they currently are viewing.  Right now, I have it set up to choose one or another based on how I imported the data.  

So, the user clicks the button and a list of forms/docs comes up:  frm1, frm2, frm3, etc. Then the user chooses one, clicks ok, and the data they had selected in the view populates the specific document.  

Is this possible?  Or is there an easier way to get at this?

Thank you

RE: R5 - In a view, creating a feature to open a list of forms

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 ?


RE: R5 - In a view, creating a feature to open a list of forms

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.

RE: R5 - In a view, creating a feature to open a list of forms

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.


RE: R5 - In a view, creating a feature to open a list of forms

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.

RE: R5 - In a view, creating a feature to open a list of forms

@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.


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close