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

Append Help

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

    Append Help

    Any idea why when I use the following Append operation is works fine, but when using it in the Script below it gives me the error �Field- and expressions-types must match.�

    This is copy of the Append operation (using the Script Recorder window)

    a_tbl = table.current()
    append.t_db = "c:ez linkpowercaminvoice header.dbf"
    append.m_key = ""
    append.t_key = ""
    append.m_filter = ""
    append.t_filter = "POSTED_TO_RECEIVABLES=.F."
    append.type = "All"
    append.m_count = 4
    append.m_field1 = "Invoice_No"
    append.m_exp1 = "Invoice_Header->Invoice_No"
    append.m_field2 = "Deposit"
    append.m_exp2 = "Invoice_Header->Deposit"
    append.m_field3 = "Adjustment"
    append.m_exp3 = "Invoice_Header->Adjustment"
    append.m_field4 = "Cust_Id"
    append.m_exp4 = "Invoice_Header->Cust_Id"
    append.t_count = 1
    append.t_case1 = "APPENDED"
    append.t_field1 = "Invoice_Header->Posted_To_Receivables"
    append.t_exp1 = ".t."
    a_tbl.append()

    This is the Script (I tried using it exactly as in the Script Recorder window, I got the same error)

    b_tbl = a_db_current_path+"invoice header.dbf"
    base = "@invoice header"

    a_tbl = table.open(a_db_current_path+"RECEIVABLES INVOICES.dbf")
    append.t_db = b_tbl
    append.m_key = ""
    append.t_key = ""
    append.m_filter = ""
    append.t_filter = "POSTED_TO_RECEIVABLES=.F."
    append.type = "All"
    append.m_count = 4
    append.m_field1 = "Invoice_No"
    append.m_exp1 = base+"->Invoice_No"
    append.m_field2 = "Deposit"
    append.m_exp2 = base+"->Deposit"
    append.m_field3 = "Adjustment"
    append.m_exp3 = base+"->Adjustment"
    append.m_field4 = "Cust_Id"
    append.m_exp4 = base+"->Cust_Id"
    append.t_count = 1
    append.t_case1 = "APPENDED"
    append.t_field1 = base+"->Posted_To_Receivables"
    append.t_exp1 = ".t."
    a_tbl.append()

    Thanks
    Dan
    Daniel Weiss
    EZ Link Software

    #2
    RE: Append Help

    b_tbl = a5.get_path+"invoice header.dbf" ?

    Comment


      #3
      RE: Append Help

      Thanks, but that gives me an error "Propety not found"
      Daniel Weiss
      EZ Link Software

      Comment


        #4
        RE: Append Help

        I don't think it's a problem, but your script recorder append doesn't refer to the transaction database with the "@" prepended.
        There can be only one.

        Comment


          #5
          RE: Append Help

          I tried a script exactly as in the Script Recorder window, I still get the same error
          Daniel Weiss
          EZ Link Software

          Comment


            #6
            RE: Append Help

            Like Stan, I think the problem lies with the absence of the "@", but in your base+"->Invoice_No" line. I had a similar problem a while back, trying to use a variable in one of these operation scripts. You really want your line in the script to be

            append.m_exp1="@invoice header->Invoice_No"

            Notice that on the right side of the = sign the expression is in quotes. But the expression you are using in your script doesn't come out that way. It comes out

            append.m_exp1=@invoice header->Invoice_No

            Perhaps you need something like

            base=""@invoice header"

            and append.m_exp1=base+"->Invoice_No""

            The " allows you to include quotes INSIDE your Xbasic expression.

            I'm not clear whether the first script example worked for you or not. It does seem to be missing the "@" which has always appeared when I used the script recorder to capture an append operation initially created by the genie. If the first script example didn't work, have you tried substituting

            append.m_exp1 = "@Invoice_Header->Invoice_No"

            append.m_exp2 = "@Invoice_Header->Deposit"

            append.m_exp3 = "@Invoice_Header->Adjustment"

            append.m_exp4 = "@Invoice_Header->Cust_Id"

            in that script? I know, the example in the xbasic manual shows the script as you have it, but I've found that the examples don't always work as shown.

            I also don't understand the point of using the "base" variable unless you plan to substitute a different table for invoice header.dbf at some point. If not, I would just hard code the append.m_expx = lines as shown above and drop the "base" variable altogether.


            Also, maybe "invoice header" should be "invoice_header" since A5 doesn't always like file names containing spaces.

            Comment


              #7
              RE: Append Help

              STOP! Don't look at the above message because it failed to show the critiacal backslashes. I always forget the board ignores them. Hopefully, this will displayt correctly:

              Like Stan, I think the problem lies with the absence of the "@", but in your base+"->Invoice_No" line. I had a similar problem a while back, trying to use a variable in one of these operation scripts. You really want your line in the script to be

              append.m_exp1="@invoice header->Invoice_No"

              Notice that on the right side of the = sign the expression is in quotes. But the expression you are using in your script doesn't come out that way. It comes out

              append.m_exp1=@invoice header->Invoice_No

              Perhaps you need something like

              base="&#92"@invoice header"

              and append.m_exp1=base+"->Invoice_No&#92""

              The &#92" allows you to include quotes INSIDE your Xbasic expression.

              I'm not clear whether the first script example worked for you or not. It does seem to be missing the "@" which has always appeared when I used the script recorder to capture an append operation initially created by the genie. If the first script example didn't work, have you tried substituting

              append.m_exp1 = "@Invoice_Header->Invoice_No"

              append.m_exp2 = "@Invoice_Header->Deposit"

              append.m_exp3 = "@Invoice_Header->Adjustment"

              append.m_exp4 = "@Invoice_Header->Cust_Id"

              in that script? I know, the example in the xbasic manual shows the script as you have it, but I've found that the examples don't always work as shown.

              I also don't understand the point of using the "base" variable unless you plan to substitute a different table for invoice header.dbf at some point. If not, I would just hard code the append.m_expx = lines as shown above and drop the "base" variable altogether.


              Also, maybe "invoice header" should be "invoice_header" since A5 doesn't always like file names containing spaces.

              Comment


                #8
                RE: Append Help

                Thanks Richard
                I did try this and still get the same error
                tbl = table.open(a_db_current_path+"receivables invoices.dbf")
                append.t_db = a_db_current_path+"invoice header.dbf"
                append.m_key = ""
                append.t_key = ""
                append.m_filter = ""
                append.t_filter = "POSTED_TO_RECEIVABLES=.F."
                append.type = "All"
                append.m_count = 4
                append.m_field1 = "Invoice_No"
                append.m_exp1 = "@invoice header->Invoice_No"
                append.m_field2 = "Deposit"
                append.m_exp2 = "@invoice_header->Deposit"
                append.m_field3 = "Adjustment"
                append.m_exp3 = "@invoice header->Adjustment"
                append.m_field4 = "Cust_Id"
                append.m_exp4 = "@invoice header->Cust_Id"
                append.t_count = 1
                append.t_case1 = "APPENDED"
                append.t_field1 = "@invoice header->Posted_To_Receivables"
                append.t_exp1 = ".t."
                tbl.append()
                end

                I have an other script in a different DB that works fine
                tbl = table.open(a_db_current_path+"cpsheet on order.dbf")
                append.t_db = a_db_current_path+"cpsheet.dbf"
                append.m_key = "FIELD_5-PART-FIELD_8-FIELD_9"
                append.t_key = "FIELD_5-FIELD_15-FIELD_8-FIELD_9"
                append.m_filter = ""
                append.t_filter = ""
                append.type = "Unique only"
                append.m_count = 4
                append.m_field1 = "FIELD_5"
                append.m_exp1 = "@CPSHEET->FIELD_5"
                append.m_field2 = "PART"
                append.m_exp2 = "@CPSHEET->FIELD_15"
                append.m_field3 = "FIELD_8"
                append.m_exp3 = "@CPSHEET->FIELD_8"
                append.m_field4 = "FIELD_9"
                append.m_exp4 = "@CPSHEET->FIELD_9"
                append.t_count = 0
                tbl.append()

                I think it has to do that I'm using it in a set where "receivables invoices" is a child.
                Am I correct? If yes, is there any solution?
                If I use the append operation whit a button on that form it works fine, but I don�t want the Append finished popup window to show
                Thanks again




                Daniel Weiss
                EZ Link Software

                Comment


                  #9
                  RE: Append Help

                  Will not solve the mistery, but if your saved operation works fine, you can get rid of "finished" dialog by using :append.run_silent("operation name")

                  Jake

                  Comment


                    #10
                    RE: Append Help

                    Have you run your modified script through DEBUG. The �Field- and expressions-types must match.� error sounds like Alpha doesn't think the expressions you are using match the field types where they are to go. If you step through this in the debugger you should be able to pinpoint the problem.

                    Another thought is the length and "separation" of your table names. Alpha seems to stumble sometimes handling long file names. Note that Alpha refers to your Invoice Header.dbf as Invoice_header.
                    There can be only one.

                    Comment


                      #11
                      RE: Append Help

                      Thanks Jake
                      I forgot about that I used it many times in different operations it just slipped my mind
                      Thanks
                      Dan
                      Daniel Weiss
                      EZ Link Software

                      Comment


                        #12
                        RE: Append Help

                        Thanks Stan,
                        Yes I did use the Debug, but it just gave me the same at the last line,
                        I also tried �invoice_header� but I got the error field not exist.
                        But anyway, Ill use the operation in silent mode, it works fine.
                        Thanks
                        Daniel Weiss
                        EZ Link Software

                        Comment


                          #13
                          RE: Append Help

                          As long as you've found a workable solution, that is all that counts. However, I have one script that has several append operations and uses the table.open() command to pick various tables to receive the appends. The button that runs this script is on a dummy table. You mention that receivables invoices.dbf is a child in your set. Are you running the script from a form attached to your set? I seem to use sets in a rather straight-forward, basic manner and have yet to get into anything too exotic with them. However, I've found that I sometimes have less difficulty when scripts manipulating tables are not run from forms associated with the tables. Maybe your thought about the set is, in fact, a direction to investigate.

                          Comment


                            #14
                            RE: Append Help

                            Richard thanks again
                            I actually got an idea that�s works fine. I made a dummy form the �receivables invoices� table, with a button on it that contains the script to Append I wrote, and I set an action "Button1.Push()" on the init of that form.
                            And on the Set Form I have a script that opens the dummy Form Silently and Refreshes the parent after.
                            It seems to work fine and it also gives me more lean way to add calculations to the Append, than when using the append operation
                            Thanks all for your help
                            Dan
                            Daniel Weiss
                            EZ Link Software

                            Comment

                            Working...
                            X