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

sets vs tables

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

    sets vs tables

    I'm building a typical sales app that is a conversion from a Lotus Approach app. In Approach, all the tables are linked together (primary key to foreign key), so there is a path from any record to any other record (for example, invoice->lineitem->product). In Alpha I can create a set, I'm calling it Universe, that reproduces the linkages in Approach. My question is, is there a significant performance penalty if I use Universe for all forms, browses, etc.? So far I've been creating minimal sets (i.e., link only the necessary tables for a particular form). My current database is small enough that I don't see a difference between Universe and minimal sets. Any information about what might I expect when much larger tables are underlying the sets?

    Thanks,

    Mike

    #2
    Re: sets vs tables

    It is most unusual to have an app with tables that can all be linked in any fashion. Perhaps Salesman -> Vendor Address would be an example. Fitting everything into a 1-1 set would be very limiting.

    Comment


      #3
      Re: sets vs tables

      There is no storage overhead in using sets. Sets are merely the linkage definitions. Given that, it wouldn't make much sense and would slow things down to create a browse of the universe set using only customer fields to display customer information. A browse based solely on the customer table would be the way to go. A set based on customer to invoice_header would make sense to display customer purchase history.
      There can be only one.

      Comment


        #4
        Re: sets vs tables

        The article collection at www.learn alpha.com will be invaluable to anyone coming to Alpha Five (Desktop) from Approach.

        Two articles directly pertinent to your conversion project:

        1) Simplify your application for added performance;

        and

        2) memos and browses that work

        -- tom

        Comment


          #5
          Re: sets vs tables

          Thanks to all for the responses. I was trying to be lazy, but it sounds as if, though there's no space penalty for using "Universe", there may be a performance penalty. That would seem to mean that Alpha doesn't try to figure out which parts of a set are actually used in a form. That's not unreasonable, but it would have been nice if it had been so.

          I will look at www.learn alpha.com - thanks for the pointer.

          Mike

          Comment


            #6
            Re: sets vs tables

            Don't know anything about Approach but in Alpha a form or browse is only a means of viewing the records in a table or set. If you build either a form or a browse on a set, all records in the set are available and to some extent "in the way" when you are only concerned with certain tables.

            If you view the default browse for a set you will see multiple browse rows (and parent table values) for each one to many child record. If you view the default form for a set you must navigate (page down) through the set records for each one to many child record before the parent value shown will change.

            Creating a saved browse or form and only putting child records on same doesn't change the underlying structure, only changes what you see.
            There can be only one.

            Comment


              #7
              Re: sets vs tables

              Thanks to the feedback I've gotten, it's occurred to me how to do an experiment that will answer my question conclusively. Let's say I have two tables, A with 20 rows, and B with 3 rows. Each row in A is linked to one row in B, so a set formed by AB will have 20 rows. If I do a browse of AB and display only the columns from B, depending upon how the set is scanned, I should get either 20 rows, or 3 rows. The result depends upon whether the way sets are scanned is by "constructing" the set on the fly, or by determining which components of the set are involved in the result, and reconstructing only the part of the set that's involved. The latter approach is evidently the way Approach processes queries on their data - in approach, I'd get 3 rows in the result. A5 always enforces the "structure" of the set, even if the entire set is not used, so we get 20 rows in the result. I've seen threads about very large SEM files. It looks as if having all my tables in one set and hanging all forms, etc off the set would possibly result in an enormous sem file, so that may be further impetus to avoid such a structure.

              That bottom line is, everyone who responded is right. Thanks again.

              Mike

              Comment


                #8
                Re: sets vs tables

                The set specification takes up very little room in the set's dictionaries. However, lots of other things get stored there.

                What? you may ask...

                Well check the help file topic: Alpha Five File Types

                To learn what's stored where in an alpha desktop app.

                Comment


                  #9
                  Re: sets vs tables

                  Mike

                  I knew the "Approach" and still using a program which made by it. The term "Joint" is called "Set" in the Alpha. Alpha does not allow the "Multiply-Line data" in their browse which Approach can do.

                  See this http://www.learn alpha.com/SimplifyY...ifyYourApp.htm

                  Comment


                    #10
                    Re: sets vs tables

                    Sandy, if you have used Lotus Agenda you will appreciate the linking that Lotus is capable of.
                    Nightmare, and then parsing/logical flow is intimidating.
                    See our Hybrid Option here;
                    https://hybridapps.example-software.com/


                    We are the
                    Department of Sunshine and Rainbows!

                    Hope restored, faith renewed, spirits lifted!

                    Comment


                      #11
                      Re: sets vs tables

                      When dbf tables are going to be very large in records and lots of fields, I tend to break them up into separate tables of 80-120 fields and link in a set one to one. Using one as the "master" table. Any one to many conections are made from the one "master".

                      I do have tables linked to the master more than one time in a couple of apps for various reasons.
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment

                      Working...
                      X