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

Help with Script Error Message: Error:Script:setvars.a5w line:9

  • Filter
  • Time
  • Show
Clear All
new posts

  • Help with Script Error Message: Error:Script:setvars.a5w line:9

    I'm having this issue where my set variables page is throwing an error on Line 9, but I don't understand why. I use the same setvars page in three other applications and I don't have any issues there. Maybe someone understands this better than I do!

    500 Internal Server Error

    Script Error
    Error:Script:setvars.a5w line:9
    session.__protected__repagency = lookupc("F",alltrim(session.__protected__ulin
    error: lookupc(F,"HYP134",REPAGENCY,[PathAlias.ADB_Path]\user,Ulink) Not an open index

    Here's what my setvars.a5w page looks like. Line 9 is the one that starts with "session.__protected__repagency"

    <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
    <meta content="text/html; charset=unicode" http-equiv=Content-Type><meta name=GENERATOR content="MSHTML 8.00.7601.17874"></head>
    dim session.__protected__repagency as c

    if eval_valid("session.__protected__ulink")
    if session.__protected__ulink <> ""
    session.__protected__repagency = lookupc("F",alltrim(session.__protected__ulink),"Repagency","[PathAlias.ADB_Path]\user","Ulink")
    session.__protected__Lastname = lookupc("F",alltrim(session.__protected__ulink),"Name","[PathAlias.ADB_Path]\user","Ulink")
    session.__protected__idno = lookupc("F",alltrim(session.__protected__ulink),"IDno","[PathAlias.ADB_Path]\user","Ulink")

    end if
    end if
    Sergeant Richard Hartnett
    Hyattsville City Police Department

  • #2
    Does the line that is throwing the error work in the Interactive window? Remove the [PathAlias.ADB_Path] and try it. If it works in the interactive window in the development environment, perhaps something happened to the .cdx file in the A5Webroot.

    Jay Talbott
    Lexington, KY


    • #3
      If I remember correctly, it is not correct to dim session variables. When you do, you create a local variable named "session.whatever" and not a session variable. Try remming out the dim and see if it works.
      Pat Bremkamp
      MindKicks Consulting


      • #4
        I disagree Pat. It's OK to dim them. Of course all session variables should be character type.

        Also note to Rich: The __protected__ part of the variable offers no benefit any more. It did in the early days of Alpha, but no more. It's OK to leave them if you want - you probably use/refer to them elsewhere and it may be a pain to change every instance.


        • #5
          I think Pat is meaning pointer(session) variables here and then he is right.


          • #6
            Jay I'm embarrassed to say that I'm not sure how to test that. And for Pat and Steve, all of my applications (and I have many) use that protected session variable code the say you see it in my original post (because that's the way I was taught to write them) and they all work fine. This is the only one I'm having issues with is this particular application. Incidentally, since I made that original post, the script error message has gone away, but now the logon information (which I display at the top of each web page) appears to be pulling data from one of my other apps. So the security function is working, but I'm getting weird information displayed from another source.
            Sergeant Richard Hartnett
            Hyattsville City Police Department


            • #7
              Jay Talbott contacted me about this problem and was able to assist me in fixing it. Thanks Jay!
              Sergeant Richard Hartnett
              Hyattsville City Police Department