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

Parsing error color equation for a database field

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

    Parsing error color equation for a database field

    Hello everyone; we've been having this error appear in our A5 v8 Build 1980 RTE: "Warning: Error parsing color equation for field inspector -> INSPECCO"
    We do use Shadow copies on each user's Desktop and we're small - less than 20 uesrs.

    Never had this error appear before and it just began a month or two ago. We have a database of inspectors, called "inspector" and the filed of "INSPECCO" is within that db representing the inspector company.
    • What is happening is when we click on our Inspector look/up query button, called "Inspector L/H" we receive this Warning pop up box with the notification above.
      • If and when it works, we'd get a pop up with all the inspector database information in it, some have colored text.
      • Often we have to close out of A5 - then reopen it and it will work but only for that session until we exit A5 again.
      • After receiving the error and hitting OK, the Inspector db does pop up but with NO Colors in it.
    • Or it will wait until we shut down a window in A5 as if we're closing it out and then the window appears last.
    I am posting some pics here too. I've been trying to scrub the database with no luck. Not anywhere near an expert in A5 at all and need assistance.

    Thank you all!
    Attached Files

    #2
    You show everything (I think) except the color equation(s) involved.
    I can appreciate the need to protect proprietary data, but as this seems
    choose colors based on data, I would expect sample data will be required
    to have any chance of successful resolution.
    Gregg
    https://paiza.io is a great site to test and share sql code

    Comment


      #3
      Ok - so since I was limited in the number of attachments in a post - I am posting the actual script here. If you need to see the actual data - I can provide a screen shot and blank out the rest.

      The data in the previous screenshots was the same except that the color appears when it works properly.

      If these script screenshots do not have the color equations - then I will have to dig to find them.

      Thanks
      Attached Files

      Comment


        #4
        I didn't see the color equations.
        fyi : you can paste your code between code tags to separate it from the rest of the post.
        Gregg
        https://paiza.io is a great site to test and share sql code

        Comment


          #5
          Quick update for anyone with possibly the same issue - and a big thanks to all who replied.

          Here's what happened in out situation. We had a user that ran into an issue that had enough admin rights to propagate a change in one of our databases. From that point, different users began writing to different 'named' databases that are supposed to have all the same info in ONE db.

          This spawned off 6 to 8 of the same databases that all had the beginning name of the db, followed by the date (which I believe was named by the individual - not by Alpha 5.

          Anyway - after a long and arduous process, I combined all the changes from the different db's and made one, as current as can be, database. From that point I deleted all of the extra databases, made a change to various scripts that were posting to the incorrectly named db's and refreshed everyone over the course of a long weekend.

          Since then, all changes are working properly and no one is having an issue.

          Thanks!

          Comment

          Working...
          X