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

How to reset a state variable

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

    How to reset a state variable

    Hi Everyone,
    The function below works great the first time it's executed,
    but if it's executed more than once it throws the error shown in
    the image below.
    Is there a way to reset the state variable without having the user
    refresh the page ?

    Any help will be greatly appreciated.

    Gregg

    2023-03-23_15-40-29.png
    Code:
    function loadStagging as C (e as P)
    dim err as p
    dim currentScript  as p
    currentScript.name = "loadStagging"
    currentScript.type = "UDF"
    currentScript.parameters = "e as P"
    dim ls as p
    dim ls.CN as sql::connection
    dim ls.RS as sql::resultSet
    dim ls.ARGS as sql::arguments
    
    dim sqlCode as p
    dim itsOpen as L
    dim itWorked as L
    dim response as C
    dim js as C
    on error goto lswtf
    sqlCode.loadStagging = <<%txt%
    select dl.label, dl.bol, dl.logged, dl.location, dl.asnmatch, dl.rowmatched, dl.distressed, dl.reporteddistressed, dl.seq
    FROM evh05warehousing.fedexinboundlog dl
    where gl.mydformat(dl.logged) >= NOW()-interval 1 month
    %txt%
    js = <<%txt%
    debugger;
    var sourceData = JSON.parse({dialog.object}.stateInfo['workingStagging']);
    {dialog.object}.stateInfo['workingStagging'] = sourceData;
    sourceData = '';
    initializeVB('fedexInboundLogVB','workingStagging')
    //debugger;
    %txt%
    debug(1)
    itsOpen = ls.CN.Open("::name::connection1")
    ls.CN.PortableSQLEnabled = .f.
    if itsOpen then
        if eval_valid("e._state.workingStagging") then
            e._state.workingStagging = ""
        end if
        e._state.workingStagging = ls.CN.ToJSON(sqlCode.loadStagging)
        response = js
    else
        response = "alert('Error accessing Server!');"        
    end if
    if ls.CN.IsOpen then
        ls.CN.Close()
    end if
    return response
    exit function 'loadStagging
    lswtf:
    texttospeech("fudge")
    err = currentScript
    err.line = "at line "+convert_type(error_line_number_get(),"C")
    err.msg = "Error in "+currentScript.name+crlf()+error_text_get(error_code_get() )
    debug(1)
    end function 'loadStaggin​
    Gregg
    https://paiza.io is a great site to test and share sql code

    #2
    I don't think it's the state variable. You ought to be able to repeatedly reuse a state variable without any problems. I mean, I certainly do. There is something going on here: ls.CN.ToJSON(sqlCode.loadStagging). I know that's not very helpful but I'd need to debug the code to figure it out.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    Comment


      #3
      When you run debug(1) what line does it fail at?
      and can you explain this to me?
      js = <<%txt%
      debugger;
      var sourceData = JSON.parse({dialog.object}.stateInfo['workingStagging']);
      {dialog.object}.stateInfo['workingStagging'] = sourceData;
      sourceData = '';
      initializeVB('fedexInboundLogVB','workingStagging')
      //debugger;
      %txt%​
      why are their 2 debug(1)'s ? - try removing and put one at the top -tell me what happens.
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)

      Comment


        #4
        Mike, ls.CN.ToJSON(sqlCode.loadStagging) loads the query results as a javascript array of objects.

        Pete,
        It fails at line 162.
        The debug(1) at line 158 is there for me to step through the code to see what's happening.
        The debug(1) in the error handler portion is there to let me see what the error info is.

        Capture.png
        Gregg
        https://paiza.io is a great site to test and share sql code

        Comment


          #5
          I agree with Mike anyhow what are you trying to do? also you should just close the connection after the query runs -
          cn.FreeResult()
          cn.close()​
          .

          See what happens
          Insanity: doing the same thing over and over again and expecting different results.
          Albert Einstein, (attributed)
          US (German-born) physicist (1879 - 1955)

          Comment


            #6
            Getting JSON data for a viewbox :)
            Since you and Lance Gurd got me to start messing around with viewboxes my javascript skills
            have improved greatly and I now prefer javascript for searching and filtering over xbasic.
            I load up a little more data than should be needed, and the searches are lightning fast, whether
            I'm searching multiple fields in one viewbox, or searching through multiple viewboxes.

            This isn't the first time AA has acted in a way other than expected for me.
            Since this seems to be an unusual issue, I opted to try something I shouldn't have to,
            which works great and solves the problem.
            Code:
            if variable_exists("e._state.workingStagging") then
                delete e._state.workingStagging
            end if​
            Gregg
            https://paiza.io is a great site to test and share sql code

            Comment


              #7
              Weird isn't it.
              Insanity: doing the same thing over and over again and expecting different results.
              Albert Einstein, (attributed)
              US (German-born) physicist (1879 - 1955)

              Comment

              Working...
              X