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

Puzzle - Set question

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

    Puzzle - Set question

    I have a set with a numeric field called "FLAGYR" in the parent. The value of this field is set to a year value e.g. "2003".

    I have a child table that I has "YEAR" as one of its numeric fields and another logical field named "ELIGIBLE".

    When I enter a record in the child: If the child record field YEAR equals the Parent field FLAGYR, I would like the ELIGIBLE in that same child record to be .T., if they do not equal I want the ELIGIBLE field to be .F.

    Is this possible?

    Thanks for any ideas.

    Dave

    David Theoharides - Principal
    Mattanawcook JHS
    Lincoln, ME 04457
    David Theoharides
    Assistant Superintendent of Schools
    Sanford School Department
    917 Main Street - Suite 200
    Sanford, ME 04073
    [email protected]

    #2
    RE: Puzzle - Set question

    You could create a default field or a calculated field in the child. The field value would be (in words): lookup the parent field, if it matches the child field then .t. else .f.

    Comment


      #3
      RE: Puzzle - Set question

      The problem is that you can not reference the fields in the parent when setting field rules or default rules for a field in the child... at least I can't!

      Thanks

      Dave
      David Theoharides
      Assistant Superintendent of Schools
      Sanford School Department
      917 Main Street - Suite 200
      Sanford, ME 04073
      [email protected]

      Comment


        #4
        RE: Puzzle - Set question

        I can think of two ways to do this, though neither is especially elegant.

        1) If a form for the parent table is open in the same session while data entry into the child table is occurring you can retrieve values from the parent table form. Check the discussion of Absolute Addresses at pg. 98 of the xbasic ref. manual.

        2) If your parent table form displays the right record, and you have a button on that form to call the child table form for data entry, you could store the necessary value in a global variable declared in the calling form. Then an identical global variable could be declared in the called form. This would pass the value to the variable in the called form, so that it could be evaluated and the appropriate data stored in the logical field in your child table.

        -- tom

        Comment


          #5
          RE: Puzzle - Set question

          David,
          Ohlen is right, you can us a lookup in field rules to get a value form a parent record. I've mostly used it to write a value to a child field. You could create a new field that has a lookup expression at the field rules level then us that field in a expression such as if(datefield=parentdatefield,.t.,.f.)

          Hope this helps
          Nick
          dbd

          Comment

          Working...
          X