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

A5 Xbasic Error Stack Log on Application Server has css error

  • Filter
  • Time
  • Show
Clear All
new posts

  • A5 Xbasic Error Stack Log on Application Server has css error

    So I was checking the error log on the application server. I just wanted to see if all looked good. The following error appeared 6 times in the error log.

    WARNING:A query parameter, form variable, or cookie name could not be used as an Xbasic variable and had to be renamed.
    Original name:85
    New name: _85
    Request Method: GET
    Request: /css/MobBlue/style.js?85

    Fortunately, nothing else did, but I know for certain this is nothing I typed, and I am stuck figuring out how I should troubleshoot it. Nothing seems to address a certain component (except for the number 85, but I don't know what that is). It does also show up on my Development Server as an error. It appeared twice when I logged in on the Dev Server, but no matter where I click, log out and back in, etc, it does not appear any additional time.

    Okay, so when a browser opens to the website, it loads the index.a5w page. The source in part shows:

    <!--Alpha Five Temporary Code Start - Will be automatically removed when page is published -->
    <!--CSS for tmpl -->
    <link rel="stylesheet" type="text/css" href="file:///C:/Program Files (x86)/a5V12/css/MobBlue/style.css">
    <!--Alpha Five Temporary Code End -->

    It only happens when I first load the page before I login. Should I even worry about it?

  • #2
    Re: A5 Xbasic Error Stack Log on Application Server has css error

    I get the same. In all my apps (I'm running on 6348 at the moment). I asked Alpha about it nearly two years ago and was told it was a problem with my CSS ...except I'm using Alpha's CSS. **Shrug** They asked for a test case but at the time I was too busy and never submitted one. I just ignore these entries.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Independent Developer & Consultant


    • #3
      Re: A5 Xbasic Error Stack Log on Application Server has css error

      Thanks Mike. I'm thinking I'll just ignore it as well. It doesn't seem to be bothering anything. I just figured I'd ask in case I'm ignoring something that I shouldn't ignore.


      • #4
        Re: A5 Xbasic Error Stack Log on Application Server has css error

        I also see the same error quite often. I'm not sure what's causing it and just finally let it be.


        • #5
          Re: A5 Xbasic Error Stack Log on Application Server has css error

          It's just a warning. Lenny says safe to ignore. I've asked for a couple years if those warnings could be removed or hidden - it makes the log file unusable. I see that build 6429 is finally managing this.


          • #6
            Re: A5 Xbasic Error Stack Log on Application Server has css error

            Thank you. I appreciate everyone's feedback. I shall consider it ignored. I do hope they manage to remove the warnings though. It's just easier to look at an error log without that filler stuff.