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

Variable type mismatch error

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

  • Variable type mismatch error

    I am getting the following xbasic stack error when running a page with a UX component on it. I am having trouble understanding what is going on. The error seems to say that there is something wrong with the alpha five code itself when it tries to run the template, or am I not understanding it at all. Help, please!

    Code:
    Thu Feb 14 16:11:52 2019
    
    Thread: AppServerWorker8
    Request URI: /__a5RunDialog.a5w?__pageName=cust_register.a5w&__dialogFilename=CUST_REGISTER&__alias=CUST_REGISTER&__unsaved=no
    Script: " /__a5RunDialog.a5w"
    Line: 169
    x_out = a5_ajax_dialog2(tmpl)
    pTemp = ValidateXFile(pRules, value)
    Script:TEMPLATE line:1
    
    Variable type mismatch: Cannot assign data of type 'L' to variable of type 'N'.
    Execution Stack:
    0#1 evaluate_shared_private(           
    0#37 OOhttpdServerClientMIME(ptemp,"AppServerMain")
    0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
    0#169 x_out = a5_ajax_dialog2(tmpl)
    Richard Urban

    Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

  • #2
    Re: Variable type mismatch error

    You'd have to post which Alpha build you're using.

    What this working? Did you update anything? Change anything?

    Comment


    • #3
      Re: Variable type mismatch error

      Ver. 12.3 Build 2682: 4435
      I am running this page and component on my test instance. I was running it before without issue. I did not change anything. I also uploaded an earlier version of the component, but the error is the same.
      Richard Urban

      Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

      Comment


      • #4
        Re: Variable type mismatch error

        Sorry, that build is a bit too old for me... 4 years. I would re-start that instance... see it that helps.

        Comment


        • #5
          Re: Variable type mismatch error

          No, that did not work. Funny thing is that the same page runs fine on other instances??? I also reinstalled the app server used for the instance, too. I also tried assigning the instance to a different app server file on the server.
          Richard Urban

          Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

          Comment


          • #6
            This error occurred erratically on one UX component, and also on another UX using that UX as a foundation. I rebuilt the UX from scratch and it is now working.
            The problem seems to be caused by repeatedly changing and saving the component, which also included commented out text and unused x-basic functions. Somehow the UX became corrupted and it sometimes worked but many times did not.
            So again, the only solution seems to be to rebuild the component from scratch.
            Richard Urban

            Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

            Comment


            • #7
              Further update. My new form was corrupted, giving the same variable type mismatch error in the x-basic stack when I changed the error settings, under properties. I was also trying to set an xbasic validation rule.
              So one or more of these settings has to do with the corruption. I cannot recover from the corruption, again.
              Richard Urban

              Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

              Comment


              • #8
                I have narrowed the cause down to validation Xbasic for the confirm_password field
                this code causes the error
                Code:
                if alltrim(e.data.password) <> alltrim(e.data.confirm_password) then
                validate_confirm_password.hasError = .t.
                validate_confirm_password.errorText = "Passwords must match."
                end if
                However, even if you comment out the code, or delete it, the error continues. However, a work-around is to change the code so that it cannot be evaluated, for instance, by specifying a field name in the evaluation code that does not exist. This does cause an Xbasic error stack log error, but the UX will submit and otherwise work correctly.

                Does anyone know what is wrong with the code above that is causing the error?
                Richard Urban

                Grocery Delivery Software for Stores and Entrepreneurs: http://www.urbangrocery.com

                Comment

                Working...
                X