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

OnPush copy then delete a record.

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

    OnPush copy then delete a record.

    Need help or a better idea.

    I would like to copy a record that I have open in a form to another table and then delete it.

    I have tried the following:

    OnPush
    Run a saved operation current record.

    I had made an operation to copy records from one table to another. It works when I test it under the operations tab. When I employ it from the form I get the following:

    Scruot: OnPush line:16
    Copy.run(operation_name,query.filter,query.order)
    Object does not support requested interface.


    I would appreciate a work around for this.

    Thanks in advance

    Bruce

    #2
    RE: OnPush copy then delete a record.

    The only thing that makes sense to me is that you might have renamed/redone the saved operation since the time you created the button?

    The button push would then be trying to run an operation that no longer existed/had a different name.

    Another possibility would be that you specified filtering on some field or variable that is not available when you push the button.

    Go to the form in design mode, right click on the button, choose the onpush event, select the action script the runs the operation, right click and select "view xbasic". You should see something that resembles

    query.filter = ""
    query.order = ""

    DIM operation_name as c
    operation_name = "some operation name here"
    If operation_name "" then
    copy.run(operation_name,query.filter)
    End if

    See if everything looks ok there.
    There can be only one.

    Comment


      #3
      RE: OnPush copy then delete a record.

      There is also a fairly new xbasic command tbl.move_record_to()


      used thusly it moves the current record to a named table

      dim tbl_source as P
      tbl_source = table.current()
      on error goto failed_to_copy
      result = tbl_source.move_record_to("yourdestinationtable")
      on error goto 0
      if result then
      ui_msg_box("Result","Record was moved")
      end if
      end

      failed_to_copy:

      ui_msg_box("Record not moved.",error_text_get(error_code_get()))

      end

      Substitute your target table for yourdestinationtable
      There can be only one.

      Comment


        #4
        RE: OnPush copy then delete a record.

        Stan,

        Awesome fix the last one worked great. Sure do appreciate the great response. I am glad that there is help out there like you.

        Thanks
        Bruce

        Comment


          #5
          RE: OnPush copy then delete a record.

          Bruce,

          This thread illustrates something you might want to keep in mind as you continue learning about Alpha Five.

          Operations, as a general rule, are intended to be run against entire tables. Multiple records are typically involved.

          When your design needs to manipulate a single record look for other alternatives.

          There's no reason to use a sledgehammer when a much smaller implement will suffice. In a multi-user networked environment using the smaller tool will pay big dividends when performance is an issue, too.

          -- tom

          Comment

          Working...
          X