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



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

Can update transaction table field during append

  • Filter
  • Time
  • Show
Clear All
new posts

  • Can update transaction table field during append

    I can't seem to update a transaction table field during an append operation.
    I have a button on a form which transfers a selection of records from a sales_order set to an invoice set. The user selects the items he wants to invoice by setting the INVOICE_FLG field to .T. and runs the procedure.
    Once the transfer is completed the append procedure is supposed to go back to the transaction table and stuff the current date into the INV_SENT field. But for some reason I get the following message

    Script:OnPush line:86
    Variable append.t_filter expression-argument is incorrect data type"


    dim shared vinvoice as n
    dim shared vsales_order as n
    dim shared vdate as d
    dim shared tbl as p
    dim shared t_db as p

    'set system date to variable

    'set the current sales order number in the sales order form to variable



    'sets current date value to invoice table

    'sets new invoice number to variable


    append.t_db = "sales_ord_detail.dbf"
    append.m_key = "str(ITEM_NUM,16,0)"
    append.t_key = "str(ITEM_NUM,16,0)"
    append.m_filter = ""
    append.t_filter = "SALES_ORD= VAR->vsales_order.AND.INVOICE_FLG=.T..AND.ISBLANK(Inv_Sent)"
    append.type = "Unique, replace existing"
    append.m_count = 12
    append.m_case1 = "EITHER"
    append.m_field1 = "Sales_Ord"
    append.m_exp1 = "@SALES_ORD_DETAIL->SALES_ORD"
    append.m_case2 = "EITHER"
    append.m_field2 = "Item_Num"
    append.m_exp2 = "@SALES_ORD_DETAIL->ITEM_NUM"
    append.m_case3 = "EITHER"
    append.m_field3 = "Partnumber"
    append.m_exp3 = "@SALES_ORD_DETAIL->PARTNUMBER"
    append.m_case4 = "EITHER"
    append.m_field4 = "Partnum"
    append.m_exp4 = "@SALES_ORD_DETAIL->PARTNUM"
    append.m_case5 = "EITHER"
    append.m_field5 = "Partname"
    append.m_exp5 = "@SALES_ORD_DETAIL->PARTNAME"
    append.m_case6 = "EITHER"
    append.m_field6 = "Quantity"
    append.m_exp6 = "@SALES_ORD_DETAIL->QUANTITY"
    append.m_case7 = "EITHER"
    append.m_field7 = "Price"
    append.m_exp7 = "@SALES_ORD_DETAIL->PRICE"
    append.m_case8 = "EITHER"
    append.m_field8 = "Creditcharge"
    append.m_exp8 = "@SALES_ORD_DETAIL->CREDITCHARGE"
    append.m_case9 = "EITHER"
    append.m_field9 = "Status"
    append.m_exp9 = "@SALES_ORD_DETAIL->STATUS"
    append.m_case10 = "EITHER"
    append.m_field10 = "Back"
    append.m_exp10 = "@SALES_ORD_DETAIL->BACK"
    append.m_case11 = "EITHER"
    append.m_field11 = "Comment"
    append.m_exp11 = "@SALES_ORD_DETAIL->COMMENT"
    append.m_case12 = "EITHER"
    append.m_field12 = "Taxable"
    append.m_exp12 = "@SALES_ORD_DETAIL->TAXABLE"

    append.t_count = 1
    append.t_case1 = "APPENDED"
    append.t_field1 = "@Sales_Ord_Detail->Inv_Sent"

    'PUTS DATE INTO TRANSACTION TABLE Why won't this work?
    append.t_exp1 = "var->vdate"


    I think I've tried every possible combination to get the append.t_exp1 to accept the date value. Please, please,please help

  • #2
    RE: Can update transaction table field during appe


    your filter expression uses the isblank() function. This function takes a character string argument.

    isblank(fieldname) won't work

    isblank('fieldname') should work

    By the way, I and others have had mixed results using isblank() with date type fields. If Inv_Sent is a date field then you might want to express the filter differently. This has been discussed in several recent message threads.

    -- tom


    • #3
      RE: Can update transaction table field during appe

      Thanks so much for the help, I could have still been at this all morning.
      I can't believe that I blew away 4 hours on the wrong part of my code when the error message quite clearly pointed to the general area of the problem (my filter). But then the error code also pointed me to the wrong line why is that?

      Do you know of a thread that covers when to use and not to use commas of both types? I know that it is one of those DUHHHH? problems that crop up all the time but perhaps someone can sort of summarise a diagnostic approach to solving problems of getting values from one place and putting it somewhere else. IT might be a great tool to put into the new Hints section.

      With regard to the field type, you are right it is a date field but I can't think of another way to filter for a blank date field.

      Regards and thanks once again


      • #4
        RE: Can update transaction table field during appe


        if cdate(inv_sent) = ""


        if len(cdate(inv_sent) = 0


        inv_sent = {}


        • #5
          RE: Can update transaction table field during appe

          Concerning the line number, the error probably isn't picked up until Alpha Five tries to evaluate the filter expression. That probably doesn't happen until the end of the script when you actually run the append()

          -- tom