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

Any Suggestions ?

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

    Any Suggestions ?

    GIVEN: the following set
    SYSNO Key SYSNO
    |--- DHI Key SYSNO+DHI Field KEYWAY,X,Y,Z..
    |---HARDWARE KEY SYSNO+DHI Fields A,B,C......

    I require a way to read the DHI table & if the field KEYWAY = "CP" then create a new set
    HSMASTER Key SYSNO+DHI 1 record per DHI record
    |---HSDETAIL Key SYSNO+DHI+OCCURANCE(=1) "

    The idea is to initially create these new records from the DHI table using fields in the SYSNO,DHI & HARDWARE tables. From there on, a HSDETAIL record will be added through a form for each occurance.
    PROBLEM:
    Its easy to create the HSMASTER record using an append but because the HSDETAIL record is a child, the key is calculated & I can not convince A5 to create it using another append.
    This is part of a larger system designed entirely without scripts or xbasic (yuk, programming). Talk about a powerful database sytem.
    Any suggestions would be appreciated. Thanks

    #2
    RE: Any Suggestions ?

    John, I'm not confident that I understand your question, but two thoughts occur to me.

    1) if the new set uses a one to one link, why not flatten its design into a single table?

    or


    2) if you must preserve the new 'set' by separating things into two table, consider using an intermediate (temporary) table. The sequence might go like this:

    - zap contents of temp table
    - append new records to the temp table, including all the fields you will need later one
    - append necessary fields to the new parent table, using the temp table as source
    - append necessary fields to the new child table, using the temp table as source


    Hope this helps.


    -- tom

    Comment


      #3
      RE: Any Suggestions ?

      Tom
      Appreciate the response
      1. Relationship is one to many
      Parent contains constant fields
      Child contains detail records of each occurance e.g. transaction date, # of widgets sold, who picked them, to date total sales, etc.

      2.The problem I am encountering is that the key of the new child file HSDETAIL, as defined in the field rules, is calculated from the parent and because the parent file (HSMASTER) is not part of the append operation it does nothing. From what I understand the append operation works on one table at at a time and not at the set level. Clear as mud ?. Perhaps I am missing something simple ?

      Comment


        #4
        RE: Any Suggestions ?

        How about this.

        The sequence might go like this:
        - zap contents of temp table
        - append new records to the temp table, including all the fields you will need later on; the goal would be to include in one long record all the parent and child table fields you will need on that particular transaction;
        - the temp table structure would also include a blank field to be used to hold the new child table key, once the append is finished, run an update operation to calculate and fill the blank child table key fields, then
        - append fields to the new parent table, using the temp table as source (omitting fields dedicated to the child table's use);
        - append fields to the new child table, using the temp table as source (omitting fields dedicated to the parent table's use).


        Does this clear up some of the mud?


        -- tom

        Comment


          #5
          RE: Any Suggestions ?

          Tom
          Will try & report back

          Thanks John

          Comment


            #6
            RE: Any Suggestions ?

            Tom
            Great idea with the single temp file. However as the child file key is a concatenated, calculated field (in field rules), passed from the parent file via the set link, A5 will not allow this field to be updated. It works if I change the field rules to input vs. calculated field. This would require a change to the field rules prior to any update which would not be practical. Any further thoughts.
            John

            Comment


              #7
              RE: Any Suggestions ?

              I always leave my linking field in the child table as 'user entered' and do not classify it in field rules as 'calculated'. To prevent the user from editing it I set it's skip value to true. This makes it easy to manipulate the field in code when needed, but the user can't get to it. Would something like that work for you?


              -- tom

              Comment


                #8
                RE: Any Suggestions ?

                Tom
                That was the ticket. Mistakenly thought link key had to be calculated. Muchos Gracias.
                On another topic have you encountered a problem with page #'s on reports. Print a report ,last page prints page # 4 of 5 yet there are only 4 pages. Seems to be tied into a group break, if I specify new page for each group it prints the first page as a blank (1 of 5).
                Thanks again
                John Gamble

                Comment


                  #9
                  RE: Any Suggestions ?

                  John, the extra pages sounds like a problem in the layout or perhaps a mismatch between the group break definition and the report's filter or query status at print time. I'd suggest you describe the details in a new message thread. It's unlikely folks will see your question since it's at the bottom of a thread covering a different issue.


                  -- tom

                  Comment

                  Working...
                  X