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

Missing Code?

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

    Missing Code?

    I have a field where I want the previous value to be automatically copied when I click the new record button. I placed this code on the button. It opens a new record but doesn't copy the previous value. What am I missing?

    parent.new_record()
    sys_send_keys("{CTRL-SHIFT-F}")

    Thanks,

    Kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    RE: Missing Code?

    I know I need to add the name of the field but that's what's stumping me, where and how to include it.

    Thanks,

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


      #3
      RE: Missing Code?

      Looks like it should work. If you rem out the send key line, can you manually do the ctrl-shift-f to get a the previous field? Reason I am asking is maybe if for some reason a query or filter on the form may be such that there is no previous record to post from. Just a thought.

      Mick

      p.s. - try doing a sys_send_keys("{ctrl-shift-f}{tab}") to see if it advances. If it does then you know the script is working at least, just not putting in a value for some reason.

      Comment


        #4
        RE: Missing Code?

        If the field in question is not at Tab stop 1, then yes you will have to set focus to the correct field.

        objectname.activate() 'jump to the correct field
        sys_send_keys("{ctrl-shift-f}") 'get the previous value
        objectname.activate() 'go to tab first data entry field

        something to that affect. I'm at home so I can't test it.

        Keep in mind that the objectname is NOT the field name. It's the name of the field itself. Right click on the field and go to properties to see (or change) the object name.

        Mick

        Comment


          #5
          RE: Missing Code?

          Nope, dosen't work. Ctrl-Shift also doesn't work when the lines are remmed out. The only code that's being recognized is the first line, parent.new_record(). I'ts as if the rest doesn't exist, including adding {tab}

          kenn
          TYVM :) kenn

          Knowing what you can achieve will not become reality until you imagine and explore.

          Comment


            #6
            RE: Missing Code?

            Hi again Ken
            Loaded A5V3 here at the house and got your result. I made a test .adb consisting of a main menu (menu.dbf)and entry form (test1.dbf) - I made a button on the menu with a button script:

            f=form.load("test1") 'loads the entry form
            f.activate() 'activates the form
            f.show() 'shows the form
            parentform.close()'closes the main menu
            f.new_record()'begins enter mode
            f:two.activate() 'jumps to objectname "two"
            sys_send_keys("{ctrl-shift-f}")'enters previous value.

            I couldn't get it to move off the field tho, except by using {tab} and {+tab}. Trying to activate() another field kind of blows up. Okay.. I'm done. Now Tom and Stan can give you the correct answer haha.

            Mick

            Comment


              #7
              RE: Missing Code?

              Well, It's almost working.

              parent.new_record()
              customer_id.activate()
              sys_send_keys("{CTRL-SHIFT-F}{TAB}")

              This works but instead of putting the previous value, it puts the next value. Since I have this set up in the field rules as auto incrementing, I've got to rethink this a bit.

              Thanks,

              ken
              TYVM :) kenn

              Knowing what you can achieve will not become reality until you imagine and explore.

              Comment


                #8
                RE: Missing Code?

                Ken,

                Will a CANEDITFIELD event on the field in question that is being
                incremented work to prevent the incrementing when CTRL-shift-F is
                applied ?

                efs

                Comment


                  #9
                  RE: Missing Code?

                  Ed,

                  Good Thought. I put: sys_send_keys("{CTRL-SHIFT-F}") on the table's field rule for the field. Alpha doesn't provide the CanEditFild event for the field when it's on a form, It has to be done in the table's field rules. Anyhow, it has no effect. I think your suggestion will work if the right combination of code is used between the event on the field rule and the button.

                  Thanks, I'll keep fiddling with it.

                  kenn
                  TYVM :) kenn

                  Knowing what you can achieve will not become reality until you imagine and explore.

                  Comment


                    #10
                    RE: Missing Code?

                    Hi Ken,

                    Quick and off the top of my head, the way to do this is with a short xbasic script that doesn't depend on sys_send_keys(). Something like:

                    t = table.open("tableName", file_ro_shared)
                    t.primary_index_put()
                    t.fetch_last()
                    vFieldvalue = t.yourFieldName
                    t.close()

                    The code assumes that you want the last record field value in record number order, if not place the correct argument in the *.primary_index_put() method.
                    This will give you the value in the variable vFieldvalue. Now do with it what you wish.

                    Good luck,
                    Jim

                    Comment


                      #11
                      RE: Missing Code?

                      Mick, Ken, Jim,

                      Q. What do the above three all have in common?

                      A. They will all be at the Mn User's Group meeting in Minneapolis on Feb 23.

                      Jim will be presenting information on Xbasic techniques. All are welcome.

                      Tom

                      Comment


                        #12
                        RE: Missing Code?

                        Oops,

                        Like I said, off the top of my head. Should be:
                        t.index_primary_put()
                        not
                        t.primary_index_put()
                        T.primary_index_put() is a little know method of the dufus object, usually works with it's sister method; t.duct_tape()

                        ..........

                        Jim

                        Comment

                        Working...
                        X