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

MySQL Dates being retrieved as type Z

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

    MySQL Dates being retrieved as type Z

    So I am in the process of moving to new servers, I have my new backend database server setup and have transferred all my data to it so it is now my live production database. However, throughout alpha anywhere I have date fields that are getting the type "Z" or "N" attached to them, is this due to a setting in alpha anywhere or in my database. Haven't seen this behavior before when using the old database and as soon as I switch back to it the issue goes away which leads me to believe there is something messed up in the database or the settings of the connection string.

    So I got the report to work on the server running in the alpha development application which wasn't working before. I got it working by putting the DATE_FORMAT function around my date field to turn it into a character field and then going into the advanced options of the datasource setup and changing it to a date field. However, when I try to actually run this from the site I get this error: "Layout type: report User cancelled at line: 557."

    Any ideas?

    It seems my issue may have been do to the fact I was running an HTML report as a PDF report (though this has always worked before), can anyone else confirm that trying to run an HTML report as a PDF report from action javascript causes an issue?
    Last edited by lilmofo812; 09-10-2018, 04:16 PM. Reason: More information

    #2
    Re: MySQL Dates being retrieved as type Z

    Standard info missing. Alpha build & type, old database server type & version, new database server & version.

    Comment


      #3
      Re: MySQL Dates being retrieved as type Z

      So the issues ended up being two fold.

      1) The "Layout type: report User cancelled at line: 557" error was due to one of the reports servers consuming almost 3GB of ram, as soon as I killed that task I was able to run my reports again (though it didn't stop me from running any other reports).

      2) The Date as "Z" type is being caused by using a UNION in the MySQL query (regardless if I use the query builder or a stored procedure) for the report, as soon as I remove the UNION the field starts showing as a date again. My other workaround stated above also works (throwing a Date_Format function around the date field causing the issue). The error I receive for this issue is "Layout type: report Error occurred parsing order expression in group Sch_date Argument is incorrect data type CDATE(Sch_date)+CDATE(Sch_Date) at line: 557" where the sch_date is a date field that I use for grouping in the report.

      Comment

      Working...
      X