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

Error when assigning session variable a value

  • Filter
  • Time
  • Show
Clear All
new posts

  • Error when assigning session variable a value

    I'm getting the following error:

    Variable already exists
    session.user_roles subproperty cannot be assigned to

    I get the error on the second line:
    dim session.user_roles as c
    session.user_roles = data.user_roles
    Is it okay to dim a session variable if it already exists? The documentation says it will just ignore it if it exists.

    This is really weird. It worked a few times, but not it keeps failing. I even tried assigning session.user_roles a constant value and still got the error.

    Also, is it okay to define character array session variables?

    dim session.user_roles[10] as c


  • #2
    Re: Error when assigning session variable a value

    Answer to your second question first: No, you can not create a session value as an array. Only Character strings are allowed.

    Have you tried NOT diming the session variable?

    Also, what value(s) are in data.user_roles?

    are you sure that the problem isn't that data.user_roles doesn't exist or contains a bad value? Because the error message leaves out what it can't be assigned to. Maybe you are trying to assign it to something it doesn't understand.


    • #3
      Re: Error when assigning session variable a value

      Another question: WHERE is this code? Is it in an Xbasic function? Is it in a server side event?


      • #4
        Re: Error when assigning session variable a value

        Hi Larry,

        Good question. I should have covered these details. The code is inside an Ajax callback function. It is not inside one of the UX component server-side events. I have not tried setting the value of session.user_roles without dimming. The variable data is a pointer (p) and data.user_roles is a character string (c) which contains the value "GroupAdmin". To rule out data.user_roles as the cause of the problem, I tried assigning session.user_roles the constant value "12345" and got the same error message.


        • #5
          Re: Error when assigning session variable a value

          Have you tried debugging the function?

          Put Debug(1) at the top of the xbasic function and watch the values of the variables.

          Especially check the value of your data.user_roles just before it gets to the error.

          If you can't do it in Alpha because you need values from outside the grid, then try saving the values of these variables to a file, again - put the save as just before the error - and see what gets dumped to disk.

          Finally, try dimming and setting a different session variable one that you are not using elsewhere in the app - just to see if it's this Particular session variable that is an issue. with a name like session user_roles, it could be a protected variable. It may also be getting confused with data.user_roles. I wouldn't share variable names like that.

          All of my session variables start with s, as in sUser_Roles. Helps be keep track.


          • #6
            Re: Error when assigning session variable a value

            Yep. I have only run in it while debugging. So you name all of your session variables like session.sMyVar1, session.sMyVar2, session.sMyVar3, etc? I will try a different session variable name.



            • #7
              Re: Error when assigning session variable a value

              I changed the code to the following and am no longer getting the error:

              dim hldUserRoles as c = data.user_roles
              session.UserRoles = hldUserRoles

              I don't know yet if it's because I'm no longer dimming the session variable to a character data type or because I'm moving data.user_roles to a temporary variable. I will find out what it takes to reproduce the problem again so I know what caused it.

              How would you store a small array of data in the session object? There is not much documentation about session variables and what the upper limits are. Is there a maximum amount of session memory you should stay under? Should you limit the number of session variables to just a handful and use another technique like storing your session data in an external flat file?



              • #8
                Re: Error when assigning session variable a value

                I don't have all the answers, but it really comes down to pushing the system until it breaks.

                Obviously, each session variable takes up memory. The less you use, the faster/better it will be. I don't know that anyone has defined the upper limits. You might ask that in a new, separate question so it will get more views.

                You can't store n array in a session object, but you could store a character separated value such as Data1|Data2|Data3|. Then parse it out as needed.

                But for arrays, you are better off just pulling up the values from a data table. There are Alpha functions to facilitate this.

                For instance, see the connection.ToPropertyArray function.

                If you discover what caused the initial problem, please post here for posterity.