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

Lost for solution

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

    Lost for solution

    Hello again,

    Believe me, I tried several searchs and couldn't find a thread related to my question :).

    I have a form that incorporates fields that will have changes made. I have put this script in the 'Can Save Record' event in field rules for records.

    '-------------------------------------------------------
    'This script checks each record after changes for errors
    '-------------------------------------------------------
    DIM TEST_YEAR AS N

    ON ERROR GOTO check
    dbh = db_current()
    If db_mode_get(dbh) = 1 .and. pap_rslt-"path_date "" {} then
    If year(date()) = year(pap_rslt-"date_acc) then
    test_year = year(date())
    Else if year(date()-1) = year(pap_rslt-"date_acc) then
    test_year = year(date()-1)
    End if
    If year(pap_rslt-"path_date) "" test_year then
    ui_msg_box("ATTENTION!!!","You have entered an invalid date for Pathologist.",16)
    ui_msg_box("EDIT PLEASE!","Please correct changes before saving record! Thank You!",64)
    fetch_prev(dbh) ---------------------
    card_resynch() ---------------------
    A_CAN_DO = "F" --------------------- Lines of concern!
    End
    End if
    Select
    Case pap_rslt-"cyt1_date "" {}
    If year(pap_rslt-"cyt1_date) "" test_year then
    ui_msg_box("ATTENTION!!!","You have entered an invalid date for Cytologist#1.",16)
    ui_msg_box("EDIT PLEASE!","Please correct changes before saving record! Thank You!",64)
    End if
    Case pap_rslt-"cyt2_date "" {}
    If year(pap_rslt-"cyt2_date) "" test_year then
    ui_msg_box("ATTENTION!!!","You have entered an invalid date for Cytologist#2.",16)
    ui_msg_box("EDIT PLEASE!","Please correct changes before saving record! Thank You!",64)
    End if
    Case pap_rslt-"cyt3_date "" {}
    If year(pap_rslt-"cyt3_date) "" test_year then
    ui_msg_box("ATTENTION!!!","You have entered an invalid date for Cytologist#3.",16)
    ui_msg_box("EDIT PLEASE!","Please correct changes before saving record! Thank You!",64)
    End if
    End Select
    End if
    End

    Check:
    err = error_code_get()
    msg = error_text_get(err)
    ui_msg_box("Error", msg)
    RESUME NEXT

    It works as far as not saving the any of the data, but after encountering the A_Can_Do = "F" , it will not remain on the same record? Is there any way I can get it to stay with the original record for corrections? As you can see, I have tried fetching, but that doesn't seem to work? The script is attached to the Path_date field in the field rules.

    Any help appreciated - Thanks in advance :)

    Mac

    #2
    RE: Lost for solution

    Instead of setting "A_CAN_DO" to a false state, Why not do a sys_send_keys("{esc}"). This will, in effect, cancel the change. We do this a lot, and the system seems to stay on record. After that, do an obj_goto to place yourself back into the namrd field (object) ie:

    field: pap_rslt-"path_date
    object on form: path_date

    then code is
    sys_send_keys("{esc"})
    obj_goto("path_date")
    end

    Try this.

    Tom

    Comment


      #3
      RE: Lost for solution

      Tom

      Thank you sir - I shall check this one out. I'm not sure what I did right at this moment, but any idea is truly appreciated :)

      Mac

      P.S.
      wish I had your experience :) and knowledge of programming

      Comment


        #4
        RE: Lost for solution

        Mac,

        I appreciate your praise, but I'm not sure it is well placed.

        I did notice in your code that you are using 2 "ui_msg_box" lines for each message. You can make one box with a couple of lines in it.

        ui_msg_box("ATTENTION - PLEASE EDIT!!!","You have entered an invalid date for Cytologist#1."+chr(13)+"Please correct changes before saving record! Thank You!",16)

        The chr(13) is a line feed character, giving you a second line in the msg_box. Looks a little cleaner.

        Tom

        Comment


          #5
          RE: Lost for solution

          Tom,

          Thanks again :) I finally noticed this little trick in V6. Wish I new about that a few yrs ago :).

          Thanks bunches for your ideas and help Tom :)

          Mac

          Comment

          Working...
          X