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
Devcon 2020 Goes Virtual! LEARN MORE >

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

SET Design Bug?

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    SET Design Bug?

    Although I�ve been using Alpha products for years, I think I came across something that may be a bug. I really hate using that word because most of the time we learn it�s actually user error, and of course I am no exception to that user error rule. However, I came across something this morning that I cannot figure out. Maybe I am doing something wrong or maybe there really is a bug? That�s why I need some help.

    I have a set design that is driving me crazy. It is a small one-to-many app that functions like a checkbook. I have no problem with the functionality of the design, but I have a concern reference the display order of the child records.

    Even though I used Form properties to order the CHILD records by Trans_Date, they still display in Rec_No() order. I went to the custom browse and ordered the child records by DTOC(Trans_Date} and even that didn�t help. No matter what I did, Alpha insisted upon initially displaying the child records from tblTransaction in Rec_No() order.

    I thought this was bizarre and found it quite frustrating. So after several failed attempts to correct what I thought was a very simple problem, I decided to try something I haven�t done in awhile. I went into �SET DESIGN�, I selected �Edit Link� for tblTransactions, and then I set the display order of the child records to

    DTOC(DATE_TRANS)

    Low and behold, that did the trick. Now my child table transaction records were properly sorted and the set opened showing the first record in the table by date order. That was exactly what I wanted, but this was when I discovered something very strange and the reason for this post.

    Please note: The parent � child tables are linked One-to-Many by the [Acct_No] field.

    After editing the set as described above, when entering new records into the child table, the Acct_No is no longer automatically entered into the child table. As you can imagine this totally ruined any attempt at data entry via the Set, something I�ve never seen before.

    Can another Alpha veteran please try this and see if they get the same results. This happens with both my custom form/ custom browse and it also happens when I tried it with the basic default form for the set. I am using the latest download posted last night.

    Am I missing something? Am I doing something wrong? Or is this really a bug?

    Thanks,
    Robert
    Tags: None
    #2
    RE: SET Design Bug?

    Robert,

    I believe setting the set child order to DTOC(DATE_TRANS) bascially creates a child link by expression. This prevents the linking field from being entered when you add a child record. So that part is not a bug as far as I know. I usually use a popup dialog to enter the child record in such cases filling in the linking value w. xbasic.

    As far as the form properties goes, I don't know why it isn't working for you. Sorry.

    Peter
    Peter
    AlphaBase Solutions, LLC

     [email protected]
    https://www.alphabasesolutions.com

    Comment

      #3
      RE: SET Design Bug?

      The order expression set in the form properties no longer works for me either. It worked fine in build 1431_1038, but not in the two patches since, so I've gone back to 1431_1038.

      Specifically, the problem is in a form based on a set called "Invoices". The parent table is "Invoice_Header" which has a one-to-many link to "Lineitems". "Lineitems" also has a one-to-one link to its own child table, "cassettes". The form has an embedded browse which displays the "Lineitems" and their associated records in the "cassettes" table.

      In the form properties, under the "filter/order" tab, I selected "Lineitems" and set the order expression based on a field in the cassettes table. This field does not appear in the embedded browse. Does this have anything to do with why the order expression doesn't work anymore?

      I noticed that the release notes for patch 1450_1040 was supposed to fix a bug in which "Setting a filter or order expression for a one-to-many child table
      did not work." It was working fine for me before the patch, but now isn't. Am I missing something here?

      Nathan

      Comment

        #4
        RE: SET Design Bug?

        Hello Robert and Peter,

        Setting the child table order should not effect the link. If it did then it would not make any sense, as one could not define the link value at the parent level as it would potentially be different for each child.

        I went to the AlphaSports database and in the invoice set, placed a child order based on another character field. Doing this did disrupt the set linking, with parent records no longer showing their children.

        Appears to me that something is not working correctly or, as Robert said, I'm missing something.

        Robert, this isn't an answer to your question, but have you tried to order the child records via an the form's onInit event, ordering the records there by setting the 'order_expression' value?

        Thanks,
        Jim

        Comment

          #5
          RE: SET Design Bug?

          Hi Jim:

          If I understand what you�re asking, yes I created my own solution which incorporates three relatively scripts that I wrote. The primary one kicks in via the form�s OnActivate Event, which sets the display order of the child table exactly as I want. I have a 2nd script on a button, which displays only child table transactions that occurred in the last 31 days, and a 3 rd button script which reverts back to displaying all records.

          Without those scripts, the child order expression remains locked into Rec-No() order.

          So yes, I personally can get around the problem, but that�s not the issue for me. If I tell an Alpha user, who doesn�t understand Xbasic, they can easily and quickly set the display order of the child table via the Form�s properties, it doesn�t seem to work. At least it�s not working on my computer and I�ve received a couple of email messages from others who said they are having the same problem.

          So that�s the issue for me, setting a display order expression by clicking on a child table in Form Properties does NOT work on my computer, and apparently I�m not alone. At this point in time, I don�t know if this is an issue facing just a few people, or one that�s universal. That�s why I would like to hear from others, advising they can, or cannot, set the display order expression via Form properties.

          As for your 2nd point reference the linking field, I think Peter G�s comments were right on the money. Although one would normally think that setting the display order of the child table in SET design, should have no impact upon the set�s linking field, it apparently does. The only logical answer seems to be Peter�s, Alpha must sort child records by creating an expression that replaces the original linking field.

          In my particular case, the original linking field of [Acct_No] was apparently replaced by the following expression:

          Acct_No + CDATE(Trans_Date)

          That's why the link no longer works. What do you think?

          Robert

          Comment

            #6
            RE: SET Design Bug?

            Hello Robert,

            >>As for your 2nd point reference the linking field, I think Peter G�s comments were right on the money. Although one would normally think that setting the display order of the child table in SET design, should have no impact upon the set�s linking field, it apparently does. The only logical answer seems to be Peter�s, Alpha must sort child records by creating an expression that replaces the original linking field

            Comment

              #7
              RE: SET Design Bug?

              [This makes no sense to me. If putting a sort order changes the linking value and breaks the link between parent and child, then what is gained?]

              Chapman, I agree with you 100%, that's why I was wondering if the behavior I observed is a bug?

              Comment

              Previous template Next
              Working...
              X