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

Parent Child Issue

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

    Parent Child Issue

    Scenario: I created a one-to-many set where as �Subscribers� database is parent and �Subscriptions� database is the child. Databases are linked by �AcctNo� field.

    Objective: Give the �YorN� field in the �Subscriber� database a �Y� value if a subscriber has a subscription expiring on a specific date (ExpDate) input with a dialog box.

    Procedure: I designed an Update Records operation. It compares the child records �Enddate� field with the expiration date and assigns �Y� to the parent�s �YorN� field if found�
    Field is YorN
    Expression is �Y�
    Condition is Var->ExpDate=Subscription->Enddate

    Problem: The �YorN� field in the �Subscriber� database is valued at �Y� ONLY if the expiring subscription in the child database is the last child record entered for that subscriber. Since a subscriber may have subscriptions for several publications, the expiring subscription may not be the last on record.

    In alpha 4, I used the following Global Update�
    Field is YorN
    If(Var->ExpDate=Subscription->Enddate, �Y�,YorN)
    This leaves the YorN field at �Y� if a subsequent non-expiring subscription is encountered. I can�t make this work in Apha 5.

    Thanks for any help.
    Bob

    #2
    Re: Parent Child Issue

    Are you saying: you want the �YorN� field in the �Subscriber� database to be "Y" if ANY of the subscriptions expired?

    If so, use exist().

    Comment


      #3
      Re: Parent Child Issue

      yes, but the expiration dates are in the child subscription database... Where do I use exist() and what should I use for the 3 arguents? Sorry, I'm new to Alpha 5...

      Comment


        #4
        Re: Parent Child Issue

        You use exist instead of the if() for the Field YorN
        You need to create an index for th echild table, using the expiration date
        Then, in the YorN, you use the expression:
        If (exist(..............),"Y", "YorN")
        Check the help file for to learn how to use exist()

        Comment


          #5
          Re: Parent Child Issue

          Bob,

          I suggest you define an update operation for the Subscriber table. Set the YorN field to "N" for all records.

          Then define a post operation in the Subscriptions table. Post a "Y" to the related record in the Subscriber table but only if the Enddate field in your Subscriptions table is equal to or earlier than the user supplied date.

          Unless I'm missing something you don't need to use your set for this.

          Example is attached. Unzip contents to an empty folder. Open form1 to find an explanation.
          Last edited by Tom Cone Jr; 04-22-2007, 10:12 PM. Reason: Attach example.

          Comment


            #6
            Re: Parent Child Issue

            The post records operation works well. Thanks for the help. I now can set the �YorN� field to �Y� for all subscribers with a subscription ending on the date that was input. I also use a second post records operation to null out the �YorN� field if the subscription has been renewed.

            Now, I want to create a simple report that prints subscribers based on �Y� in the �YorN� field and �detail� only the subscriptions with the ending date that matches the variable date. For some reason, the detail�s filter does not recognize the variable date�s value and ALL of the subscriber�s subscriptions are detailed. To test this, I place the variable date field in the header of the report... it produces a blank field when the report is run. The post records operations recognize it, but not the report.

            FYI: The variable date is input with an X dialog box when a button on a form is pushed. It is the first event, the date is input with a calendar and Global is selected.

            Any ideas? Thanks in advance.
            Bob

            Comment


              #7
              Re: Parent Child Issue

              Bob, yes. Suggest you begin a new thread since the initial question has been solved. When you begin the thread, post a zipped copy of the database with instructions for us to follow in your footsteps in order to see the problem.

              Comment

              Working...
              X