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

Progress Report

  • Filter
  • Time
  • Show
Clear All
new posts

  • Progress Report

    This is primarily for J. Brightbill and Tom Cone....

    'Date Created: 05-Apr-2004 06:22:20 PM
    'Last Updated: 01-Aug-2004 12:20:07 AM
    'Created By : Jerry Brightbill
    'Updated By : Dick Coleman
    'Create an XDialog dialog box to prompt for parameters.

    DIM v_itemname as C
    DIM v_category as C
    DIM v_media as C
    DIM v_bookname as C
    DIM v_booknumber as C
    DIM v_pagenumber as N
    DIM v_disknumber as N
    dim v_type as C
    DIM v_location as C
    dim v_value as N
    dim v_createdate as D

    DIM varC_result as C

    heading_string = "Enter Item Information"
    ok_button_label = "&Save"
    cancel_button_label = "&Cancel"

    '----------------- Error message Code -----------------
    DIM v_msg as C

    error_ok_button_label = "&OK"

    error_dlg_code = ""%dlg%
    {image=$sys_warning}{sp} |{text=30,3:v_msg};

    dlg_code = ""%dlg%
    {position=remember="Enter Item"}
    {background=Blue White}
    {frame=1,1 Use the TAB key or your MOUSE to move between fields. DO NOT use Enter or Esc! }
    Item Name:|[60.80v_itemname] ;;
    Media Type:|[25.80v_media];;
    Item Type:|[15.80v_type];;
    Media Name:|[60.80v_bookname];;
    Media Number:|[6.80v_booknumber];;
    Page Number:|[3.80v_pagenumber];;
    Disk Number:|[2.80v_disknumber];;
    {frame=1,1 Use MOUSE to select buttons }
    "15=ok_button_label!OK" "15=cancel_button_label!CANCEL";;

    dlg_event = ""%code%
    tbl ="b_items")

    if recno("b_items")"15
    ui_msg_box("Demo Overload","You have exceeded the limits of this demo application. No additional items can be accepted!!",ui_ok)
    end if

    case a_dlg_button = "enter" .OR. a_dlg_button = "esc"
    if (.not. ("OK"$ui_dlg_ctl_current("Enter Item") .or. "Cancel"$ui_dlg_ctl_current("Enter Item")))
    a_dlg_button = ""
    end if

    case a_dlg_button = "OK"
    case v_itemname = ""
    v_msg = "The Item Name is a required field"
    a_dlg_button = ""
    ui_dlg_ctl_goto("Enter Item","[60.80v_itemname]")
    case v_category = ""
    v_msg = "The Category is a required field"
    a_dlg_button = ""
    ui_dlg_ctl_goto("Enter Item","[30.80v_category]")
    case v_media = ""
    v_msg = "The Media Name is a required field"
    a_dlg_button = ""
    ui_dlg_ctl_goto("Enter Item","[25.80v_media]")
    case v_location = ""
    v_msg = "The Location is a required field"
    a_dlg_button = ""
    ui_dlg_ctl_goto("Enter Item","[25.80v_location]")
    end select

    case a_dlg_button = "CANCEL"
    if alltrim(v_itemname - v_category - v_media - v_type - v_location - v_bookname - v_booknumber) "" ""
    chk = ui_msg_box("Cancel","Do you want to cancel entry? ",UI_QUESTION_SYMBOL+UI_YES_NO)
    if chk "" UI_YES_SELECTED
    a_dlg_button = ""
    if is_open("b_items")
    end if
    end if
    end if
    end select

    varC_result = ui_dlg_box("Enter Item",dlg_code,dlg_event)

    Do I pass????????


  • #2
    RE: Progress Report

    Gee, that looks familiar. I am glad you could adapt it for your needs. The only change I would make is to move the "demo check" to the code under the ok event. Then the table won't be opened and closed for every change, but only when they try to commit a record. You could run that check before the xdialog even opens and just set a logical variable. Then replace the table code with a check for the value of the variable.



    • #3
      RE: Progress Report

      I like the idea of a check on the way 'in'...
      There's more on that page than you can see....
      the things I have learned just trying to understand all the 'procedures' that you outlined in the presentation... and all the 'cross-referencing' that had to be done to make other scripts work...
      I really thank you for the 'insight'


      • #4
        RE: Progress Report

        I am really going to look into checking for 'recno()' on the way in to the item input...
        The reason I put it where it is, was because it fires at the end of the first field input, which just cuts down on the 'inputter' typing b4 they get the error msg...