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

Query by Form Doesn't Fire "onfetch" Event

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

  • Query by Form Doesn't Fire "onfetch" Event

    We are finding that the "onfetch" Event is not fired when our user's perform a Query By Form, using A5/v9's standard menu, toolbar, ctrl+B, etc.

    Can anyone confirm this to be the case in their environment... or is it just us, or is there some reason we should not expect it to fire the Event?
    "all things should be as simple as possible... but no simpler"

    Mike

  • #2
    Re: Query by Form Doesn't Fire "onfetch" Event

    No, I can't confirm this. I'm using XP Pro Sp3. I put the following script in the OnFetch event of the Products form in AlphaSports:
    Code:
    trace.writeln("OnFetch has fired.  Record# "+ltrim(str(recno())))
    I open the form. I do Ctrl-B and specify ">25" in the Cost field. I run the query. The onFetch fires when focus shifts to the first record that meets my filter criteria.

    When you test your form does the current record meet the filter specs of your query? If so no fetch would be necessary.

    Comment


    • #3
      Re: Query by Form Doesn't Fire "onfetch" Event

      Sorry for my delayed response to your reply... I'm not sure what/why our filtering would have anything to do with it?

      We have code in the onfetch which we thought would fire for every record retrieved. That, does not seem to be the case. That is, regardless of how or why a record is presented to the user... i.e. regardless of the filter imposed... we want our code to be executed before the user is presented with a new record.

      Sorry if I'm not making sense... or have confused the situation.
      "all things should be as simple as possible... but no simpler"

      Mike

      Comment


      • #4
        Re: Query by Form Doesn't Fire "onfetch" Event

        Hi Mike,

        Any chance that you could post a sample of the app you have the problem with?
        Regards
        Keith Hubert
        Alpha Guild Member
        London.
        KHDB Management Systems
        Skype = keith.hubert


        For your day-to-day Needs, you Need an Alpha Database!

        Comment


        • #5
          Re: Query by Form Doesn't Fire "onfetch" Event

          Yes, I will, as soon as I have a few minutes... but, in the mean time... it seems to be every time, all the time, every form. To recreate:

          1) edit any form, adding a msgbox (for example) to the onfetch event.
          2) save and run the form.

          At this point we receive the msgbox, then the first record is presented.

          3) use the standard toolbar nav buttons to cycle through records.

          As we navigate through the records, we receive the msgbox for each record.

          4) click the standard toolbar button for QBF, enter criteria for a record that exists, click "run query."

          And we do not receive the msgbox for the record presented.

          5) cancel the query, using the standard toolbar button... loop... same results as above... i.e. it seems the onfetch code is not executed when in QBE mode... or whatever mode we are in :-)
          "all things should be as simple as possible... but no simpler"

          Mike

          Comment


          • #6
            Re: Query by Form Doesn't Fire "onfetch" Event

            Works fine in v8. Must be a bug in v9.

            Comment


            • #7
              Re: Query by Form Doesn't Fire "onfetch" Event

              Michael I don't get your results using the Invoice form in AlphaSports in vers 9. I'm using build 2077_3259. OnFetch triggers the message box after the successful query runs, and each time I fetch a new record in the filtered subset displayed by the query.

              Comment


              • #8
                [Variation] Query Doesn't Fire "onfetch" Event

                I seem to be experiencing a similar issue of 'onfetch' event not firing when a record is pulled up as a result of a query.

                I have an form onfetch that populates a number of variables when a record is fetched.

                It works fine with regular record navigation, searches, etc. The variables always reflect the record.

                However, if I am working on a group of records that were the results of a query, the first record that is displayed gets the onfetch, but if I change a record so it no longer meets the query criteria, the variables do not get updated. They retain the values of the record I had been working on.

                It seems really like when a record is saved and the query refreshes itself, the resulting record fetched ignores the onfetch.

                I tried onInit, variations of refresh, resynch, etc. with no better results.

                I finally ended up just putting a button on the form to force the variables to refresh, but it's kind of hokey.

                Any thoughts would be appreciated.

                A5V9 Desktop (Build 3252)

                Comment

                Working...
                X