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 Variable value

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

    Append Variable value

    I am trying to append records from file A "receiving" to file B "names", but I want to be able to change the Date_Into_System value based on input from a dialog box. The code below gives an error "....references a non-existent field....". I can't understand what I'm doing wrong. INPDATE is the variable I am trying to set via the dialog and append to the Date_Into_System record. Can anyone point me to the problem?

    ' *****************enter date to use
    DIM INPDATE as C

    result=ui_dlg_box("Date of Log File (MM/DD/YYYY)",""%dlg%
    Date to use: [30INPDATE];
    "OK"
    %dlg% )

    DIM Append as P
    a_tbl = table.open("names")
    append.t_db = "receiving"
    append.m_key = "ROLL_NUMBER-PO_NUM-SIZE"
    append.t_key = "ROLL_-P_O_-SIZE_QTY"
    append.m_filter = ""

    ' only non-blank records
    append.t_filter = "P_O_"\"\""
    append.type = "Unique only"

    append.m_count = 12
    append.m_field1 = "Name"
    append.m_exp1 = "@Receiving-"Description"
    append.m_field2 = "Stylenum"
    append.m_exp2 = "@Receiving-"Color"
    .
    .
    .
    append.m_field10 = "Uop"
    append.m_exp10 = "@Receiving-"Uop"

    append.m_field11 = "Date_Into_System" '***error occurs**
    append.m_exp11 = "CTOD(INPDATE)" '***** here ******

    append.m_field12 = "Roll_Number"
    append.m_exp12 = "@Receiving-"Roll_"

    #2
    RE: Append Variable value

    If I got the error

    "....references a non-existent field....".

    I would think that Alpha didn't know that

    CTOD(INPDATE) referred to a variable.

    So I'd try

    CTOD(var-"INPDATE)
    There can be only one.

    Comment


      #3
      RE: Append Variable value

      Stan,

      Thank you for the help. One of these days, I might be able to think like you..and be able to fix these minor probs I keep on encountering.

      Thanks again.

      Jim

      Comment


        #4
        RE: Append Variable value

        Only meant to show the problem solving process. Usually the error messages aren't nearly that helpful.

        Never hurts to clarify things with the var-" prefix, though it often isn't required. Calc-" is another prefix that is good to get in the habit of using.

        Good luck.
        There can be only one.

        Comment


          #5
          RE: Append Variable value

          I agree with Stan... even though Alpha usually recognizes variables as such, I almost always use var-" and calc-" prefixes, if nothing else but for my own clarification later on when I (or others) need to modify/understand the code. It's good practice, like commenting your code.

          Bob Emery

          Comment


            #6
            RE: Append Variable value

            Thanks again, both of you. I appreciate those bits of insight that develop over time....great to share them.

            Jim

            Comment


              #7
              RE: Append Variable value

              Stan,

              I've tried your suggestion, and wrote a little routine just to update a field in a table using the var-" prefix. Still have problems in that the update does not occur unless I change the "CTOD(var-"INPUTDATE") back to just the function "DATE()". Not what I want obviously.

              I'd appreciate anymore feedback on how do do this.This is the portion of code I can't make work:

              ' *****************enter date to use*********
              DIM INPUTDATE as C
              DIM DATE1 as D
              result=ui_dlg_box("Date of Log File (MM/DD/YYYY)",""%dlg%
              Date to use: [30INPUTDATE];
              "OK"
              %dlg% )
              ' ****************Convert it and check for correctness
              DATE1=CTOD(var-"INPUTDATE)

              message_text = " Date to use is "+DATE1+crlf(2)+ "Is it OK to proceed?"

              operation_result=ui_msg_box("Update Operation",message_text,UI_OK_CANCEL+ UI_FIRST_BUTTON_DEFAULT+ UI_INFORMATION_SYMBOL)
              If operation_result "" ui_ok_selected then
              end
              end if
              '******** Date shows correctly so go to the update section
              .
              .
              .
              update.field17 = "DESCRIPTION"
              update.expr17 = "W_UPPER(DESCRIPTION)"
              update.field18 = "LOGDATE"
              update.expr18 = "CTOD(var-"INPUTDATE)" '"--line of interest
              update.field19 = "AMOUNT"
              update.expr19 = "1"
              .
              .
              .
              a_tbl.update()

              Stan Mathews wrote:
              -------------------------------
              Only meant to show the problem solving process. Usually the error messages aren't nearly that helpful.

              Never hurts to clarify things with the var-> prefix, though it often isn't required. Calc-> is another prefix that is good to get in the habit of using.

              Good luck.

              Comment


                #8
                RE: Append Variable value

                We've run into one of those quoted character string inside another quoted character string situations.

                From the interactive editor

                update.expr18 = "CTOD(var-"INPUTDATE)" 'your first attempt

                ? UPDATE.EXPR18
                = "CTOD(var-"INPUTDATE)"'"-not what we want

                VAR-"INPUTDATE="08/16/2004" '"-make an assignment like your script would

                update.expr18 = "CTOD('"+var-"INPUTDATE+"')" '"-drop the variable into the expression properly

                ? UPDATE.EXPR18
                = "CTOD('08/16/2004')"

                and we get the desired result.
                There can be only one.

                Comment

                Working...
                X