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

a5w info page - error in Session.Variables.Keys

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

    a5w info page - error in Session.Variables.Keys

    Every time I look at my a5w_info page, and anyone else's for that matter, I see an error similar to the following in the Session.Variables.Keys

    Exception has been thrown by the target of an invocation. Cannot implicitly convert type 'System.Collections.Generic.Dictionary.KeyCollection' to 'System.Collections.Specialized.NameObjectCollectionBase.KeysCollection' ===== Stack Trace Follows ===== System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.CSharp.RuntimeBinder.RuntimeBinderException: Cannot implicitly convert type 'System.Collections.Generic.Dictionary.KeyCollection' to 'System.Collections.Specialized.NameObjectCollectionBase.KeysCollection' at CallSite.Target(Closure , CallSite , Object ) at A5INETServerIntegration.A5INETVariablesProxy.get_Keys() --- End of inner exception stack trace --- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams) at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args) at CA5TypeDotNet.GetProperty(CA5TypeDotNet* , datum* ResultValue, CA5DataString* Name, vector >* Args, CA5Pointer* Instance)

    I get the error even if I have just logged in. Is this something that I am doing? My apps are working fine, so this doesn't seem to affect anything, but it would be nice if there were no unexplained errors at all!

    #2
    Re: a5w info page - error in Session.Variables.Keys

    Sounds like you're not using the current build. The build that had that error had lots of other problems too -- I know, because I ran into them and asked.
    -Steve
    sigpic

    Comment


      #3
      Re: a5w info page - error in Session.Variables.Keys

      I am only 1 version behind. There are actually some issues in the current pre-release that fix things I need, so I'm trying to wait for the next release.

      But I'll wait until I upgrade to check out that particular issue again, thanks for letting me know. (Everything else is working fine!)

      Comment


        #4
        Re: a5w info page - error in Session.Variables.Keys

        There is, essentially, no difference between official releases and pre-releases. It's best just to find a release that fits your needs for features and has the fewest bugs that will affect what you're doing.

        Comment


          #5
          Re: a5w info page - error in Session.Variables.Keys

          Pre-releases are put out every day with the latest bug fixes and the latest code.

          I believe (or at least I sincerely hope!) that actual releases are given a bit more testing before being labeled as official releases.

          In order to avoid tygers, I like to keep my development version in sync with all of the production versions for which I am responsible.

          And I try to avoid using prereleases on production servers unless absolutely necessary.

          Are you suggesting that is no longer necessary?

          Comment


            #6
            Re: a5w info page - error in Session.Variables.Keys

            I don't think it was ever necessary. Official releases receive no more quality control than any other release. I had the same process as you... but came to understand the release philosophy. An official release is always followed by a pre-release which fixes bugs in the official release. Usually the week following an official release is a series of pre-releases with bug fixes for the official release.

            But... it's a cycle. To get a fix for the official release, you usually must install a pre-release. That pre-release can contain new code... with bugs. Another pre-release comes out to fix those pre-release bugs... plus official release fixes... and contains new code... and you're stuck in a cycle.

            There should be 3 tracks of releases... not 2.

            1 : Official
            2 : Official bug fixes
            3 : Pre-release containing bug fixes and new code.

            Comment

            Working...
            X