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

Problem with Topparent.find(var_key)

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

    Problem with Topparent.find(var_key)

    I am new to Alpha Five.

    I used Topparent.find(var_key) in a form to find and read a record in a table. It managed to find and read the correct record and display its data in the form. Then I used Recno() to check the record number of the current record in the table and discovered that the current record pointer has not been reset to point at the record which has just been read.

    How can I reset the current record pointer to point at the record which has just been read ? Thanks in advance.

    #2
    Re: Problem with Topparent.find(var_key)

    I will hazard a guess that you are checking the record number from a second instance of the table and not the instance of the table that is opened by the form.
    Andrew

    Comment


      #3
      Re: Problem with Topparent.find(var_key)

      As an example, let's say the table had 500 records. I ran a script to open the form and the current record pointer pointed at record # 501. I tried to read, say, record number 300 and succeeded in doing so. However, the current record pointer still pointed at record # 501.

      Comment


        #4
        Re: Problem with Topparent.find(var_key)

        Let us see the script.
        Andrew

        Comment


          #5
          Re: Problem with Topparent.find(var_key)

          The same thing happened even if I clicked open the form directly.

          Allow me to phrase my question in a different way. Are there known bugs with topparent.find(var_key) ?

          If I execute topparent.cancel() BEFORE topparent.find(var_key), then topparent.find(var_key) will find the correct record, display its contents and reset the current record pointer to point to that record. If I don't, then it won't reset the current record pointer. Is that how it is supposed to work ?

          Comment


            #6
            Re: Problem with Topparent.find(var_key)

            Need to see the script.

            Comment


              #7
              Re: Problem with Topparent.find(var_key)

              The form has about 20 fields.

              The user is expected to input the value of a record key into field # 1 and press <Enter>.

              The CanDepart Event of field # 1 contains the following codes :

              DIM GLOBAL S_KEY AS c
              S_KEY = parentform:Field1.value
              DELETE var_key_target
              var_key_target = S_KEY
              topparent.find(var_key_target)
              topparent.allow_change(.t.)

              Comment


                #8
                Re: Problem with Topparent.find(var_key)

                KDM, try this:

                S_KEY = parentform:Field1.text

                Comment


                  #9
                  Re: Problem with Topparent.find(var_key)

                  That didn't work.

                  Comment


                    #10
                    Re: Problem with Topparent.find(var_key)

                    or

                    maybe S_KEY = this.text

                    and you might try it in the OnDepart event as well
                    Tim Kiebert
                    Eagle Creek Citrus
                    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                    Comment


                      #11
                      Re: Problem with Topparent.find(var_key)

                      Code:
                      DIM GLOBAL S_KEY AS c
                      S_KEY = parentform:Field1.[COLOR="Red"]text[/COLOR]
                      'DELETE var_key_target
                      'var_key_target = S_KEY
                      [COLOR="Red"]parentform[/COLOR].find([COLOR="red"]S_KEY[/COLOR])
                      [COLOR="red"]parentform[/COLOR].allow_change(.t.)

                      The changes in red illustrate how I'd handle this assuming the form is based on a single table.

                      KDM, if your form is based on a set of tables, or if you're using a subform in your form, these ideas probably won't work, especially if you're searching in a child table. It would help if you showed us the entire script, so we can see the steps that are being followed up to the point you check the record number of the found record. Recommend you zip your database and post it here with instructions for us to follow so that we can trace your steps leading to the problem. This permits us to see the entire script while it's running in context.

                      Comment


                        #12
                        Re: Problem with Topparent.find(var_key)

                        I just realized that topparent.find(var_key) did not work because the form was in "ENTER" mode. Topparent.cancel() apparently changed the mode in such a way that topparent.find(var_key) was able to work properly.

                        Is there another way to change the mode from "ENTER" to "FIND" before executing topparent.find(var_key) ?

                        Comment


                          #13
                          Re: Problem with Topparent.find(var_key)

                          I like this approach:

                          The button script that initiates the find should check the mode of the form and prompt the user to cancel or save pending edits and then end. If the form is not in CHANGE or ENTER mode then the script should proceed to do the find.

                          Comment


                            #14
                            Re: Problem with Topparent.find(var_key)

                            I am converting an ancient DOS/clipper program and I am trying to preserve the look-and-feel of the original program. Therefore I am trying to do things that may appear to you to be rather unorthodox.

                            Having said that, I have no problem with topparent.cancel() except that it displays the data from the record being pointed to by the current record pointer immediately before topparent.find(var_key) finds and displays the data from the record found. As a result, the form appears to blink for maybe one-tenth of a second and I would like to stop that from happening.

                            Is there any way to stop topparent.cancel() from displaying the data from the record being pointed to by the current record pointer ?

                            Comment


                              #15
                              Re: Problem with Topparent.find(var_key)

                              Is there any way to stop topparent.cancel() from displaying the data from the record being pointed to by the current record pointer ?
                              There are alternatives, depending upon the context in which you are doing this. Are you doing the find as / when the form is opening? I thought you were doing the find when the form was already open, in which case there'd be no blink... the current record would already be on screen. Describe your complete sequence for us.

                              Are you aware that the message board permits file uploads? This might be one of those cases where attaching a zipped copy of your database would help us help you, provided you also include instructions so that we can find the right form, script / button and run it in the same sequence you're struggling with.

                              Comment

                              Working...
                              X