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

db limits: 40 tables per set; lookup tables too?

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

  • db limits: 40 tables per set; lookup tables too?

    Newbie question:
    Just starting on my v9 database in earnest (medical practice/patient records).
    I know that a set is limited to 40 tables. I only anticipate at present maybe 10 "secondary" tables that would be connected to the primary table which would be called "patient_tbl". The patient table would have just a few fields (name, DOB, pt_id, address, ss#.) "Secondary" tables linked to the patient table would be broken into various medical grouping, (signs, symptoms of their illness, radiologic studies, pathology, labs, etc).
    Many of the fields in the various table would be such that a lookup tables would be needed.
    For example, separate tables for medications, diseases, allergies, operations, etc.
    Each lookup table is pretty basic, 2 fields: a unique ID field and the "info" field. For example, the medication lookup table would have the fields med_id, and meds. (As you might imagine the number of meds is very large so a simple list would not work. This really is the case for nearly all of my lookup tables.)
    I can get the secondary table to "draw" from the lookup table without having to link the tables in a set structure, using the field rules and setting the linking field, source/fill choices and I set it as a drop down list box.
    However, my instints say that it would be better if it was "truly" linked in the set in a parent/child fashion. However, if I do that I would rapidly exceed the 40 tables per set rule. By the same token I am invoking some type of linking function and I don't know if that is going to gum up the database.
    This must be a common issue. Please advise. Thanks!

  • #2
    Re: db limits: 40 tables per set; lookup tables too?

    rule of thumb: a set should have the least possible number of tables. I see no advantage to linking "lookup" tables. The bigger the set, the greater the hit on performance and the greater the possibility for problems.
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    Comment


    • #3
      Re: db limits: 40 tables per set; lookup tables too?

      However, my instints say that it would be better if it was "truly" linked in the set in a parent/child fashion.
      In my experience.....

      Any of the functions that name a table deliver their result independently of the current context. When designing a field rule lookup the table to be used as the source of values must be named just as the function lookup() requires. To me this means there is no need/benefit from including the named table in set for lookup purposes.

      I also seem to remember that you can even lookup() or table.external_record_content_get() to a table that is not part of the current database if you specify the full drive_path_tablename.
      There can be only one.

      Comment


      • #4
        Re: db limits: 40 tables per set; lookup tables too?

        There's no good reason to include your lookup souce tables in your data entry sets.

        The article "Simplify your Applications for Better Performance" at www.learnalpha.com is a useful resource when designing sets. Recommended.

        -- tom

        Comment


        • #5
          Re: db limits: 40 tables per set; lookup tables too?

          Thank you all for your informative answers. That is exactly what I needed to know.
          This is a great forum.

          Comment


          • #6
            Re: db limits: 40 tables per set; lookup tables too?

            Stan, you can also open forms in other adb's - but you have to use the @with the form
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment

            Working...
            X