Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Table lookup, to use in a form.

  • Filter
  • Time
  • Show
Clear All
new posts

    Table lookup, to use in a form.

    I�m trying to make a application, and one of the basics is the ability to display several different records frm one db simultaneously in a set called by the parent of the set.
    The situation is of one person renting more than one item from a products list.
    We use it for:- cost list for rental on invoice for different line items, different drivers/employees for the same company, the same part used for repair of different machines, etc.

    eg, one person renting several library books.

    I have tried following this (very helpful) message board advice, but I am still stuck.

    I have now:-
    a person list db.
    -linked to: one to many, person number field to linking field.
    a linking db, two fields. linking field, and machine number field.
    The machine number field of the linking db, has field table lookup to the the db of the machine db.

    In that configaration nothing much works, just a browse of the linking field; with it�s two fields.

    If I have a further link in the set, one to one from the linking db machine number to the machine db, machine number field it works.
    I get the machine details I want from the lookup field. BUT, only for the last record; not for the several I need. If I try one-to-many, nothing.

    I am sure I am missing something simple, but not getting it.
    Attachments don�t seem to work here I can�t get to print or read them, and I certainly consider myself a newbee at all computor stuff.
    This is a continuation of my question;- Sets, using child db twice in form does�nt work dtd approx 1/12/2001


    RE: Table lookup, to use in a form.


    The linking of tables is not really hard, but it isn't easy either.

    to get a list of what one has rented/sold to a customer, a link something like.

    Parent - customer - linked on acct field
    one to many
    child - machines ( rented/sold items ) - linked on acct field

    Once this is done - you can make a browse of machines in your form based on the set to view all rented/sold items to that account.

    This is a simple one, but hard if you are new to this.

    You may already be way ahead of this but Linking fields is kinda logical - getting the info out is almost the reverse sometimes.

    Hope it helps


      RE: Table lookup, to use in a form.


      Assume three tables:

      Customers - contains contact info on each customer
      ItemsRented - contains list of items rented by a customer
      ProductsList - contains details on each item rented.

      Put a customernumber field in Customers and ItemsRented. Use it to link Customers table one to many to ItemsRented.

      Put an itemnumber field in ItemsRented and ProductsList.
      Use it to link ItemsRented one to one to ProductList.

      Your set has a parent table, Customers.
      It has a child table ItemsRented
      It has a grandchild table ProductsList.

      Base your form on the set.

      The foregoing assumes you do not want to store the descriptive details for each item inside the ItemsRented table.

      In some apps it would be simpler to have a two level set, omitting the grandchild table. However, you've have to store the descriptive information on each item rented inside each ItemsRented record. This could be done using a table lookup to the ProductsList, filling in the desired fields in ItemsRented table.

      If this is all greek to you, and you continue to feel like in you're in over your head, there's nothing wrong, but you may want to hire someone to build it for you.

      -- tom


        RE: Table lookup, to use in a form.


        Thanks for your help.
        I have done what you suggest and it works as you say. I guess the problem is that is not what I need.

        I need the result of one person -taking out many library books/garage car repair -using many parts/one teacher -has many students, etc. etc.
        It must be a common requirement.

        I do need to display and use the descriptive details of the product list, and so far I can do that either:-

        a)-by having a link, one to one, between child linking table and grandchild table. The problem I have with this it only displays one record at one time, logically. I need to display all the records and only those, in the grandchild table that are selected in the parent table. I suppose I could display one record, then copy that info to fields in the parent, then go to the next grandchild record etc. That just seems pretty long-winded for what I want.

        b)-by having corresponding fields filled in the child table by the grandchild lookup table, and arranging the pop-up. It seems to want to pop-up all the records in the child linking table, but I guess I can use some filtering to get only what I select in the parent in the pop-up. The problem with that approach seems like I'll end up reproducing all of the grandchild db eventually. That will end up with reproduced, non-current db�s in lots of linking tables thruout the application; and there will be many of them. Keeping each db current will be a nightmare, I thought relational db�s were to avoid that, as well as other things.

        I was wondering if there is a practical approach in using either method:-
        (a) basically, but using a method to show more that one record in the browse table on the form Is that possible? It seems to me to be the best approach, and having a one to many link from parent to child linking tables I thought would have done it, but I can only get it to show the one record. But it still looks up the grandchild table and retains it unless I would pack it or something afterwards.
        I suppose I can use this approach as follows:- instead of a linking table with a corresponding record, one field only, of all the grandchild records, I could use a linking table with only one record in which I fill in the first field from the parent table. Then have the first field post its info to the second field, which then gets the info in one record of the lookup table. I could use a separate linking table, for each parent field which required the info from the granchild db. It seems to me I would be using lookup tables to do the job a relational db, but it should work?

        (b) basically, but only to pop-up the selected grandchild records from the parent table, and then afterwards to pack the child linking table to eliminate clutter build up.

        (c) I still feel there must be simple approach that I am missing!

        Thanks for your time and help.


          RE: Table lookup, to use in a form.


          Why not zip the database you are developing and attach it here for us to see? Include a text file explaining which forms and tables you want to use, and outlining, in detail, what it is you are trying to accomplish... and where it's failing.

          -- tom


            RE: Table lookup, to use in a form.


            Here's a simple example of the two level model I described before.

            Unzip the attachment to a separate folder. Do not mix it with your development work.

            -- tom


              RE: Table lookup, to use in a form.

              Hi Tom,

              I think I finally have the answer to this. I�m still checking it out and will advise. Your input has been a great help; thanks.



                RE: Table lookup, to use in a form.

                That's good news. Let us know what you come up with.

                -- tom