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 and multi-column keys

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

    Sets and multi-column keys

    Hi

    I'm building a data entry app that exports data for uploading into a big RDBMS. I'm trying to replicate the data structures as far as possible.

    One parent-child relationship relies on a 2 column primary key. I can't see any way to achieve this in Alpha - the set editor only seems to allow for a single column foreign key.

    I guess I could set up a new technical key on an auto increment field in Alpha and strip it out again while exporting, but this seems ugly. Can Alpha really only work with single column keys, or am I missing something?

    #2
    RE: Sets and multi-column keys

    Alpha suggests table key fields with the same name as linking keys when designing a set. If you don't agree with the suggestion you can choose another field. When you use the smart button to the right of the field box the top choice is always "expression" where you can define a complex key.
    There can be only one.

    Comment


      #3
      RE: Sets and multi-column keys

      Geoff,

      If I understand you correctly you need the "expression" choice for the linking key. When you go to the prompt for the linking key you will get a drop-down list of the field names from which to select. At the top of that list is the choice of "expression". Upon selecting that, the expression builder will appear which allows you to combine separate fields for your link.

      BTW, the term "column" is for the most part a spreadsheet term outside the realm of Alpha software development. For that reason, it is suggested that you start thinking in terms of "fields" instead. Until you break that ice, you may have more difficulty in referncing the documentation, postings, etc. My 2 cents.

      Steve

      Comment


        #4
        RE: Sets and multi-column keys

        Geoff,

        You can make a two column primary key. Just use field rules
        to make the column calculated.

        EG: two_col_key_tbl
        col1 C 10
        col2 C 5
        col3 C 5

        in field rules, col1 = col2 + col3

        Then just create an index on col1.
        To insure uniqueness, enter the expression
        Col2+Col3 as the uniqueness test for both
        col1 and col2.

        Comment


          #5
          RE: Sets and multi-column keys

          Steve,

          fyi, in the database world, column is an appropriate name as
          it applies to tables. Field, in most cases, applies to forms
          and usually refer to columns in a table.

          Comment


            #6
            RE: Sets and multi-column keys

            Melvin,

            Maybe your generalization for all database software is correct but I specifically referred to "Alpha software". You may "usually refer to columns in a table" but most all of the CHM's, tutorials, etc. for Alpha refer to elements of a table as "fields".

            Comment


              #7
              RE: Sets and multi-column keys

              Hi guys

              Yikes - talk about hiding a feature! Thanks for pointing it out.

              """""
              BTW, the term "column" is for the most part a spreadsheet term...
              """""

              In my experience, "column" is the term used in RDB textbooks, the docs of Oracle, SQLServer, Postgres etc, and in the SQL-92 standard ( http://tinyurl.com/bkuwf ). It's even part of the language: "ALTER COLUMN"

              "Field" is more colloqial, I think. But certainly many people (including Alpha it seems) tend to use it to mean a column...

              Anyway, this is a bit OT, so I'll shut up!

              Comment


                #8
                RE: Sets and multi-column keys

                Hi

                I knew there had to be a way - turns out there's more than one!

                I'll play with both methods.

                Thanks for the suggestion... I'm so used to SQL I find it hard to get into the Alpha way of doing things...

                Comment

                Working...
                X