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



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

A5goes weird after running this script

  • Filter
  • Time
  • Show
Clear All
new posts

  • Tom Cone Jr
    RE: A5goes weird after running this script


    In general what you're seeing is Alpha Five's effort to do what it thinks you want it to do. I'll be happy to look further, but will need a working model of your database, and instructions on how to replicate the issue.

    In my earlier post, I was thinking of using load() to open the form but not show it until after the query had run. If you get zero records returned you can close the form without ever showing it.

    -- tom

    Leave a comment:

  • Graham Wickens
    RE: A5goes weird after running this script

    I agree that your suggestion will work, but if there are no matches to be found the form lists the lot in record order, which rather defeats the object. I do most of my work in Browse tables, when I use this script and make a choice, all the correct values are put in the correct places. The odd thing I have now noticed is that although the "cancel changes" and "save record " tabs are available , nothing happens when I click either, also if I scroll down to the next record, I would expect the two tabs to "Grey out" but they dont. But if I swap to form [F8] the record is saved and the two tabs are "Greyed out" until such times as a record is changed.
    What is happening here ???

    Leave a comment:

  • Tom Cone Jr
    RE: A5goes weird after running this script

    If the Operator form is based on the Operator table, I'd do this differently. Instead of opening an instance of the table, running a query, and then opening the form...

    I'd load the form, and then run the query through the form, or using the instance of the table which the form itself loads...

    Not sure if this will solve your problem, just suggesting another approach you might try.

    -- tom

    -- tom

    Leave a comment:

  • Graham Wickens
    started a topic A5goes weird after running this script

    A5goes weird after running this script

    I wrote this script some time ago, but have just come across a problem. It works OK, does all that I want it too, BUT, after running the script the system ignores any changes in any field that I try to input. After restarting A5 things are OK again. It is called from a right-click-menu.

    The Script: Asks for a Location, searches the "Operator" table and lists any operators that are at that location. a double-click on the list then loads the relevant values into the logfile table record.

    dim global new_operator as c
    dim global new_op_unique as c
    dim global new_c1 as c
    dim global new_c3 as c
    dim global new_colour as c
    reply=upper(ui_get_text("Base Search for Operator","Enter Location Name"))
    if reply = "" then
    goto done
    end if"Operator")
    query.filter="containsi(base,reply) .or. containsi(area,reply)"
    query.description="Find All Oper"
    case n > 0
    if is_object("Operator Lookup")
    :Operator Lookup.activate()
    form.view("Operator Lookup","Dialog")
    end if
    :Operator Lookup.close()
    case n = 0
    ui_msg_box("Base Search","No Operators on File for "+UPPER(Reply)+ " Found.")
    end select
    Operator.text = new_operator
    Op_unique.text = new_op_unique
    c1.text = new_c1
    status.text = new_c3
    colour.text = new_colour

    I guess that the code is in fact quite correct, just that I am possibly missing something to put A5 back where it was before the script was called???