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

Announcement

Collapse

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

Nested Tables

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Nested Tables

    I have had Alpha versions going way back. I have never solved a problem in any of them with nested tables. My main use is a libary catologing system. It has a lookup table for authors. Things will work fine until I have to have a second lookup of information to post to the Authors table before posting the info. to my main table. After that I have to close the table I am using and reopen it. My lookups do not work when trying to enter the second record. Does anyone know what may be wrong?

    #2
    RE: Nested Tables

    Does the second lookup call the same table that was opened initially?

    You might check the table lookup field rule in your primary table to make certain that the lookup is configured to permit the user to add records to the lookup table.

    -- tom

    Comment


      #3
      RE: Nested Tables

      The attachment illustrates a multilevel lookup situation.

      The primary table, Students, has a Name field. This field has a table lookup field rule, which uses the LookupNames table as its source.

      The user is permitted to add new entries to LookupNames. While doing so a table lookup rule for that table permits them to choose names from the MasterNamesList table.

      All of this can be done without closing the original data entry form.

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

      -- tom

      Comment


        #4
        RE: Nested Tables

        Thanks! I appreciate the help so much. I took a minute to look over the settings, indexes and such in my program and compare them to yours. I did not find anything. I did delete the stack of indexes I no longer use.

        Here is some more details about my problem. Everything seems to work when my lookup tables are small and my master table is also small. Several years ago, I could solve the problem for two master records by using a small "data entry table." Now that my lookups are large, this does not work at all. My setup is similar to the sample, but each time I enter a record into the master using the double nested tables, I have to close the master table and reopen it before my lookups will work on the master table.

        As for size, I don't know if it is the issue or not. My master table has 2200 records and is 942,000 bytes. It has three lookup tables. The first lookup table looks up the author name. It contains the name, biographical data, and a author code. This one has 1600 records and 88,000 bytes. This author code has to be looked up in a second table with 2700 records and 65,000 bytes. The setup is very similar to your sample.

        There is also a lookup table for the classification of the books according to the Dewey Decimal system. It now has 5000 records and is 510,000 bytes.

        The last lookup is a subject lookup with only 700 records and 63,000 bytes. I have basically quit using it.

        Like I said, everything works find for just a few records in each. The trouble is, this is impossible to be functional. Everything also works fine if the nested table setup does not have to look up the author code. I have fiddled with settings, but never found anything to solve the problem.

        Any more ideas?

        Comment


          #5
          RE: Nested Tables

          If you want to zip it all up and email it to me I'll take a look at it over the weekend.

          -- tom

          Comment


            #6
            RE: Nested Tables

            The tables you describe are small. I don't think size is the issue. I vote for problems with the links between your tables. Care to give a few details?

            Bill
            Bill Hanigsberg

            Comment


              #7
              RE: Nested Tables

              Hi All!

              This is embarrassing. I think I figured out the problem. I was running my tables outside my set setup. Now that I made new forms that are based on the set system, things seem to work just fine. I'll be testing things over the next week to see how things happen.
              --Clinton

              Comment

              Working...
              X