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

Copy will not run.....

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

    Copy will not run.....

    I created a Copy operation.... using the genie..... inserted "Copy.run("blank")" into an onpush for a button on my form. Shutdown A5... opened application... go to form with the button... push button... tells me "No such table".... so what part of working with the genie did I get wrong?

    #2
    RE: Copy will not run.....

    Oh... if I go to the operations tab in control panel... it runs just fine.

    Comment


      #3
      RE: Copy will not run.....

      Argh! On second thought... nevermind... I dont need a backup. Problem solved.

      Comment


        #4
        RE: Copy will not run.....

        Jeff,

        I just experienced this problem. What was the solution?

        Thanks,
        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: Copy will not run.....

          Well here is *one* solution. The problem was the same. The export.run() command would work in a script run from the control panel or interactive window but would fail when run from a button.

          I understand the issue and I understand the solution. Still, I am going to demonstrate action scripting to a group in a couple of weeks and I would like to be able to show a simpler way to run an operation from a button as the solution detailed below could stick some people as exotic. Shouldn't action scripting be able to handle this?

          Moreover, I thought a script created a new session. If so, having the button run a script which runs the operation should solve the problem but it doesn't. So I must be misunderstanding something.

          All help gratefully received.

          Bill



          Msg ID: 7945
          Subject: RE: export error
          Author: Selwyn Rabins
          Date: 10-17-2002 1:47 PM
          File:


          replace the line:

          :export.run("expsubinvoices")

          with this


          cmd = cvendno"
          export.field2 = "poheadertemp1->cinvno"
          export.field3 = "poheadertemp1->cinvdate"
          export.field4 = "poheadertemp1->desc"
          export.field5 = "poheadertemp1->amtreleased"
          export.field6 = "poheadertemp1->glacct"


          but, the export was defined as:


          export.field1 = "poheadertemp->cvendno"
          export.field2 = "poheadertemp->cinvno"
          export.field3 = "poheadertemp->cinvdate"
          export.field4 = "poheadertemp->desc"
          export.field5 = "poheadertemp->amtreleased"
          export.field6 = "poheadertemp->glacct"

          so you get an error.

          Bill Hanigsberg

          Comment


            #6
            RE: Copy will not run.....

            could *strike* some people as exotic. (I'll take care of sticking it to them.)
            Bill Hanigsberg

            Comment


              #7
              RE: Copy will not run.....

              Continuing this little conversation with myself, I found another way.

              If you capture the xbasic for the operation (copy in my experiment) and substitute table.get() for table.open() in the line
              a_table = table.open("your source table's name")

              you eliminate the error because you are using the current session of the table. Hence, no 2nd session with a different alias.

              You also have to eliminate the a_table.close() line at the end as you would be trying to close the primary table of the current session and would (I think) create another error.

              Still, I wonder if action scripting shouldn't be able to cope with the context issue.

              Bill
              Bill Hanigsberg

              Comment


                #8
                RE: Copy will not run.....

                Bill, good morning.

                Your second approach is how I've always done it in Version 4. Capture the script the saved operation is using, and then modify it to run against the same instance of the tables used by the current form. Depending on the level of experience of your audience, it occurs to me that this might be a good way to show them the script recorder.

                -- tom

                Comment


                  #9
                  RE: Copy will not run.....

                  Hi Tom,

                  Agreed on both points. And the "recorder" utility is better in 5 as you don't have to run a saved operation to see its code as you can peek at the xbasic and copy it to the clipboard.

                  Of course, the script recorder is nice too.

                  But the environment I was working in last night is carried over from version 4 and the button to run the saved operation worked from 4.3 to 4.5. I don't remember when I wrote it but it was a while back.

                  So this is a difference between 4 and 5 which needs to be managed. The question I raise is how best to do so and avoid confusing users of action scripting.

                  This "application" is so simple that I never captured the operation's low level xbasic. I just made a button to run it.

                  For the record, it is a simple copy operation which copies certain records in the current table (on which the application's sole form is based) to an empty second table of identical structure.

                  All the best,
                  Bill
                  Bill Hanigsberg

                  Comment

                  Working...
                  X