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

Help - Validation/Field rules

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

    #16
    Re: Help - Validation/Field rules

    Stan, that was it. One minor problem left.

    Have I mentioned how much I appreciate your help? :-)

    How would I allow the user to cancel out? Right now if I enter a ticket number of less than 9 char. it yells at me properly. However it won't let me cancel out of the record without having to enter a record.

    Thanks once again.

    Comment


      #17
      Re: Help - Validation/Field rules

      Originally posted by Playball335
      Stan, that was it. One minor problem left.

      Have I mentioned how much I appreciate your help? :-)

      How would I allow the user to cancel out? Right now if I enter a ticket number of less than 9 char. it yells at me properly. However it won't let me cancel out of the record without having to enter a record.

      Thanks once again.
      I may be wrong but I don't think that is doable. You get the warning when the user exits the browse, not when they change rows. What could happen is that the user enters an incorrect ticket, moves to another row, then exits the browse. At that point there is no way to tell which record should be deleted.

      I suppose it would be possible to process all the child records and delete any with incorrect ticket numbers but a lot of work. Why not just have the users finish the entry with garbage and delete it when done?
      There can be only one.

      Comment


        #18
        Re: Help - Validation/Field rules

        What is happening works to a degree.

        a user moves into the browse to add a ticket, realizes for instance they are in the wrong work order and want to escape. The CanDepart statement will not let them leave the record.

        Is there anything I can do to let them escape without saving the record?

        Comment


          #19
          Re: Help - Validation/Field rules

          Here's my 2 cents: Why not use the CanSaveRecord to test for a blank or invalid entry in the field and cancel the Save, then warn the user why his data was not saved? That will at least give him the opportunity to try again.
          Robin

          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

          Comment


            #20
            Re: Help - Validation/Field rules

            I'm not sure this thread is still active.
            I've a journal entry screen with browse1. Columns in browse1 are ac_code, dr_amount, cr_amount.
            If I enter a value in Dr_amount, cr_amount should become 0 and vice versa.
            The code is something like this
            if Dr_amount>0
            cr_amount=0
            endif
            if cr_amount>0
            dr_amount=0
            endif
            Where will I validate this? Please help

            Comment


              #21
              Re: Help - Validation/Field rules

              That creates a chicken or egg conundrum.
              In a browse you work at a record level so which comes first?
              Maybe when you start to edit a record you must zero both.
              Common Dr/Cr practice does not use two amount fields - separation occurs in presentation.

              Comment


                #22
                Re: Help - Validation/Field rules

                I did manage to do this.

                I've a journal entry screen with browse1. Columns in browse1 are ac_code, dr_amount, cr_amount.
                If I enter a value in Dr_amount, Cr_Amount should become 0 and vice versa.

                How?

                Select Table - Design - Field rules
                Select Dr_Amount-Events-Field Events-onWroteField

                if gl_tran->Dr_Amount>0 then
                gl_tran->Cr_amount=0
                end if

                Select Cr_Amount-Events-Field Events-onWroteField

                if gl_tran->Cr_Amount>0 then
                gl_tran->Dr_amount=0
                end if

                Comment


                  #23
                  Re: Help - Validation/Field rules

                  When I make a copy of a table I miss most of the field rules. I right click the table to copy then select duplicate.
                  Any suggestion on this?

                  Comment


                    #24
                    Re: Help - Validation/Field rules

                    Originally posted by jacobr View Post
                    When I make a copy of a table I miss most of the field rules. I right click the table to copy then select duplicate.
                    Any suggestion on this?
                    Post a couple of images of what you do and the choices that are available. From your other posts, I'm guessing that you are using v10 or v11, not v7 like this forum is for..
                    Al Buchholz
                    Bookwood Systems, LTD
                    Weekly QReportBuilder Webinars Thursday 1 pm CST

                    Occam's Razor - KISS
                    Normalize till it hurts - De-normalize till it works.
                    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                    When we triage a problem it is much easier to read sample systems than to read a mind.
                    "Make it as simple as possible, but not simpler."
                    Albert Einstein

                    http://www.iadn.com/images/media/iadn_member.png

                    Comment

                    Working...
                    X