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

Remedial fetch-find help

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

  • Remedial fetch-find help

    Working on my second app, a bit more complex than my first one, and I'm having my first run-in with coding:

    I have a table called deals with a field called deal_no, and index called deals. The idea is that if the user enters a new record and it's an existing deal, I don't want an error message for an existing record, I just want to find the record and populate the fields after the user presses the Enter key. If I'm thinking about this right, I'm trying to attach code to the deal_no field's CanWriteField event. Just to test it, I have:

    option strict
    dim tbl as p
    dim nrec as n
    tbl=table.current()
    nrec=tbl.fetch_find(tbl.deal)
    iif(nrec>0,ui_msg_box("Found","Found"),ui_msg_box("Not Found","Not Found"))

    (The iif statement is just to see if the coding above is working before I try to figure out how to retrieve the record and populate the fields). I set the primary index to deal in the form's init event. When I open the form and enter a new record with a deal number (pre-existing or not), when I press Enter I receive an error message "Expected Value".

    I've read the A5 documentation and Dr. Wayne's (excellent) book on Xbasic on this, but I know I must be missing something. Am I on the right track for doing what I want to do?

    Jack

  • #2
    Re: Remedial fetch-find help

    Wouldn't it be

    nrec=tbl.fetch_find(tbl.deal_no)
    There can be only one.

    Comment


    • #3
      Re: Remedial fetch-find help

      I thought so too at first, and that's the way I had it, but the index name is deals, so I changed it to that. In any event, I still get the same message either way.

      Comment


      • #4
        Re: Remedial fetch-find help

        Of course it might be simpler as


        Code:
        If EXIST( deal_no.value, "deals","deals")
           ui_msg_box("Found","Found")
        else
           ui_msg_box("Not Found","Not Found")
        end if
        if deal_no is the objectname of the deal_no field on the form.
        There can be only one.

        Comment


        • #5
          Re: Remedial fetch-find help

          Originally posted by grayfox5 View Post
          I thought so too at first, and that's the way I had it, but the index name is deals, so I changed it to that. In any event, I still get the same message either way.
          The fetch_find() uses an index already in effect. You do not name the index in the fetch_find().

          tbl.fetch_find(value to find in the index)
          There can be only one.

          Comment


          • #6
            Re: Remedial fetch-find help

            Originally posted by grayfox5 View Post
            option strict
            dim tbl as p
            dim ix as p
            dim nrec as n
            tbl=table.current()
            ix = tbl.index_primary_put("deals")
            nrec=tbl.fetch_find(tbl.deal_no)
            iif(nrec>0,ui_msg_box("Found","Found"),ui_msg_box("Not Found","Not Found"))
            I think something is happening to the index you have set. Try the above.
            There can be only one.

            Comment


            • #7
              Re: Remedial fetch-find help

              Stan,

              Tried that (and by the way, I also changed the index name to "deals" so that there wouldn't be any potential conflict with the table name "deal"). Still no success. The "If EXIST" snippet you wrote in the previous post did work, however. If there was a way to populate the fields from the found record based on that, I could go that way. But I figured I had to find the record number and retrieve it in order to populate the form with the found record.

              Jack

              Comment


              • #8
                Re: Remedial fetch-find help

                Can you attach a sample here? I had trouble just as you mentioned, but only when the index wasn't correctly set.
                There can be only one.

                Comment


                • #9
                  Re: Remedial fetch-find help

                  Sample attached. Thanks.

                  Jack

                  Comment


                  • #10
                    Re: Remedial fetch-find help

                    Doh! Sorry Stan, I found an error (you probably did too). I should always remember: computers won't run your code if it's wrong. I found 2 quotation marks instead of 1 in my ui_msg_box. Actually, A5 found it when I tried pasting the code into the field's OnDepart event on the form. The code now reads:

                    option strict
                    dim tbl as p
                    dim ix as p
                    dim nrec as n
                    tbl=table.current()
                    ix=tbl.index_primary_put("deals")
                    nrec=tbl.fetch_find(tbl.deal_no)
                    if nrec>0 then
                    ui_msg_box("Found Record",nrec)
                    else
                    ui_msg_box("Not Found",nrec)
                    end if

                    The code now fires, but the weird thing is that it never finds a record, whether I enter an existing deal number or not. I always get the Not Found message with a -1 value displayed in the message box.

                    I'm a bit closer now that the code is technically correct, I just need to dig a little more to figure out possibly whether it's attached to the incorrect event or some other problem on my end. Thanks.

                    Jack

                    Comment


                    • #11
                      Re: Remedial fetch-find help

                      Almost there. Turns out the correct event is not in the field rule's CanWriteField event, but in the field's CanDepart event on the form. When I type an existing deal and press Enter, I get the message box with the record number.

                      The only remaining problem appears to be the first time the form is loaded and I click the Enter New Record button. The event fires and tells me I'm on record 1, which of course I am. Maybe if I somehow load the form without displaying any records at all...

                      Comment


                      • #12
                        Re: Remedial fetch-find help

                        Try the onchange event instead.
                        There can be only one.

                        Comment


                        • #13
                          Re: Remedial fetch-find help

                          Yes, the onchange event seems to be the correct one. I've modified things though by adding a button to search/enter a deal number, and attached code to it using a hybrid of your earlier If Exist snippet (which works great) and code generated by Action Scripting. At this point, when the user clicks the button, a dialog pops up and prompts for deal number. If it's found, it retrieves that record, end of story. If it's not found, I'll give the user the option to enter a new deal. So far, so good. Thanks.

                          Jack

                          Comment

                          Working...
                          X