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

eval() function could be dangerous.

  • Filter
  • Time
  • Show
Clear All
new posts

  • eval() function could be dangerous.

    Does anyone know if the xBasic eval() function many of us have used for years has the same dangers and warnings the javascript eval() function has ?
    Gregg is a great site to test and share sql code

  • #2
    I don't see how. For one thing JS is client-side. Xbasic is server-side. A user doesn't have access to the server-side. They can't execute arbitrary server-side code.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Independent Developer & Consultant


    • #3
      Hi Mike,

      Does that line of think hold true for your client as well ?
      Gregg is a great site to test and share sql code


      • #4
        That would hold true to all of my own clients. A user doesn't have the ability to access and/or run their own server-side code from the client-side of things.
        Mike Brown - Contact Me
        Programmatic Technologies, LLC
        Independent Developer & Consultant


        • #5
          I guess I did a poor job of asking that question.
          You made the part about your server being protected quite clear,
          but you ignore the affect eval(), the javascript function, and have
          on your client's computers.
 is a great site to test and share sql code


          • #6
            I'm sorry, I'm lost now. No where do I mention using eval() client-side. Anyways, maybe someone else will answer your question.
            Mike Brown - Contact Me
            Programmatic Technologies, LLC
            Independent Developer & Consultant


            • #7
              This is what happens when I start messing around with things I should leave alone.
              My thoughts swirl around in my head, an while they're valid, the output is anyone's guess.
              Knowing that Alpha has written their own js functions, I have a feeling that several enthusiasts
              will think js eval() function is as safe as xbasic eval().
     is a great site to test and share sql code


              • #8
                Sure eval (js) is as safe as eval(xb) if you use them both serverside in Alpha. I do not mean nodejs here. I have noticed that performance in loops is better with javascript. But the real life problem is of course how to pass data between serverside xbasic and javascript.


                • #9
                  Hi KK,

                  It appears my intent was missed.
                  Alpha Software has gone out of it's way to help us deliver "safe" applications to our clients.
                  From informing us about Log4j ramifications to updating ssl/tsl keys, to strongly suggesting
                  we use sql arguments instead of regular text to prevent sql injection attacks.

                  I don't know which came first, XB eval() or JS eval(), but I am not the only one to be surprised by JS eval().
                  I was further surprise to find no mention of JS eval() in Alpha's documentation nor any mention of it's danger
                  evidenced by the warning displayed on multiple sites while looking for details on the function.

                  I could understand if this was about cobol, pascal, or react, but this is javascript, a language so prevalent
                  that Alpha Software has it's own javascript libraries that due to a well earned reputation are presumed to
                  be save by the many subscribers that pay annual fees to use this product.
         is a great site to test and share sql code


                  • #10
                    I may be missing something here, but what have the 2 functions in JS & XB got in common? If Honda put out a recall for one of their cars you wouldn't stop driving your Ford.


                    • #11
                      Using an analogy based on your question, We know Honda had a great car in the prelude (xb). Now Ford comes out with their own prelude (js).
                      The Ford looks like Honda's prelude and mostly functions like Honda's prelude, but has one important characteristic Honda does not have.
                      The Ford has a safety issue (drivers don't survive a crash with a combined speed of more 15 mph).
                      Honda knows about this difference.

                      Do you think Honda should give their clients notice of the harmful look alike ?
             is a great site to test and share sql code


                      • #12
                        Contact Alpha about it.
                        Mike Brown - Contact Me
                        Programmatic Technologies, LLC
                        Independent Developer & Consultant


                        • #13
                          I think the interesting question is when did developers decide that eval (js) is a dangerous function. Obviously it has not always considered to be a dangerous function. The danger is that it is very easy to use wrong but if it can not be modified by the user then it is not dangerous at all.

                          Actually exactly same is with sql injection. Everybody says that use arguments, you must use arguments but for sure you do not need if there is no user input.