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

Using Access SELECT SQL in Alpha5 - can't get this loop to parse

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

  • Malcolm
    replied
    Re: Using Access SELECT SQL in Alpha5 - can't get this loop to parse

    An even better solution is to retain the query in Access and set up the A5 grid builder to refer to a 'view' rather than a table - ie it refers to the the Access query. Clumsy, but it works much better than using the whole select statement in A5.

    Leave a comment:


  • Malcolm
    replied
    Re: Using Access SELECT SQL in Alpha5 - can't get this loop to parse

    OK, so it appears that my little machine hasn't enough 'grunt.' I know this because I fitted more RAM and it works OK - just. All forum users must be using big powerful machines where this problem never occurs! Still, I'm not sure why Access is able to spit it out in the blink of an eye and A5 takes perhaps 15 minutes - and it's not even on the web yet!

    Leave a comment:


  • Using Access SELECT SQL in Alpha5 - can't get this loop to parse

    There has to be a simple reason why my SQL SELECT statement won't parse in A5 - but I can't find it.

    I have a complicated 'number of weeks between two dates, except ...' field to include as a field on a report (not my idea). I'm using Access as a backend, and just to make sure that the SQL SELECT statement works as intended, I used a query in the webroot version of the Access programme to develop it. Access produces the field instantly. When I copy and paste the SQL SELECT statement from the Access query into the A5 Grid Query Builder - my machine crashes. I've imported the statement sequentially (ie bit by bit) and it works to a point, then when the loops get too long - it gets overloaded.

    I've even deleted the extra 'I' from all the 'If's.' According to my reading, an Access SQL Select statement should work in A5 - but this one doesn't. Perhaps the reason relates to my use of DateSerial(yyyy.mm,dd)? I can't find any suggestion on how to specify dates differently?

    I can't see any way of simplifying the SELECT statement - and if it works in Access - it should work in A5.

    I don't expect anyone to read through and make any sense of the SQL statement itself - but just in case anyone can see something that A5 obviously doesn't like - it is:

    SELECT Cases.CaseName, Cases.ApprovedDate, Cases.CloseDate, IIf( Datediff('ww', Cases.ApprovedDate, Date() ) > 46 , '>40', IIf(Cases.ApprovedDate BETWEEN DateSerial(2012, 1, 23) AND DateSerial(2012, 4, 6) AND CloseDate > DateSerial(2012, 10, 15) , ( DateDiff('ww', Cases.ApprovedDate, Cases.CloseDate) - 6), IIf(Cases.ApprovedDate BETWEEN DateSerial(2012, 1, 23) AND DateSerial(2012, 4, 6) AND Cases.CloseDate BETWEEN DateSerial(2012, 7, 16) AND DateSerial(2012, 10, 2) OR Cases.ApprovedDate BETWEEN DateSerial(2012, 4, 23) AND DateSerial(2012, 6, 30) AND CloseDate > DateSerial(2012, 10, 15) , ( DateDiff('ww', Cases.ApprovedDate, Cases.CloseDate) - 4), IIf(Cases.ApprovedDate BETWEEN DateSerial(2012, 1, 23) AND DateSerial(2012, 4, 6) AND Cases.CloseDate BETWEEN DateSerial(2012, 4, 23) AND DateSerial(2012, 6, 30) OR Cases.ApprovedDate BETWEEN DateSerial(2012, 4, 23) AND DateSerial(2012, 6, 30) AND Cases.CloseDate BETWEEN DateSerial(2012, 7, 16) AND DateSerial(2012, 10, 2) OR Cases.ApprovedDate BETWEEN DateSerial(2012, 7, 16) AND DateSerial(2012, 10, 2) AND Cases.CloseDate > DateSerial(2012, 10, 15) , ( DateDiff('ww', Cases.ApprovedDate, Cases.CloseDate) - 2), IIf([Cases].[ApprovedDate] Between DateSerial(2012,1,23) And DateSerial(2012,4,6) And IsNull([Cases].[Closedate]),(DateDiff('ww',[Cases].[ApprovedDate],Date())-6),IIf([Cases].[ApprovedDate] Between DateSerial(2012,1,23) And DateSerial(2012,4,6) And IsNull([Cases].[Closedate]) Or [Cases].[ApprovedDate] Between DateSerial(2012,4,23) And DateSerial(2012,6,30) And IsNull([Cases].[Closedate]),(DateDiff('ww',[Cases].[ApprovedDate],Date())-4),IIf([Cases].[ApprovedDate] Between DateSerial(2012,1,23) And DateSerial(2012,4,6) And IsNull([Cases].[Closedate]) Or [Cases].[ApprovedDate] Between DateSerial(2012,4,23) And DateSerial(2012,6,30) And IsNull([Cases].[Closedate]) Or [Cases].[ApprovedDate] Between DateSerial(2012,7,16) And DateSerial(2012,10,2) And IsNull([Cases].[Closedate]),(DateDiff('ww',[Cases].[ApprovedDate],Date())-2),( DateDiff('ww', Cases.ApprovedDate, Cases.CloseDate)))) ) ) ) )) AS Duration
    FROM RTLBDetails INNER JOIN (Cases INNER JOIN (Schools INNER JOIN CasesSchools ON Schools.SchoolID = CasesSchools.SchoolID) ON Cases.CaseID = CasesSchools.CaseID) ON RTLBDetails.GroupID = Cases.ReferringRTLBID;

    Trust me - it produces a great result in Access!
Working...
X