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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Quick Report and SQL query problem

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Quick Report and SQL query problem

    I'm still in my 30 day test period and having an issue with Quick Report and SQL query.

    I am working on converting an Access mdb to MSSQL. I ran the SSMA program to convert the Access tables (only) to MSSQL 2008 Express. I am running A5 with a connection to the SQLEXPRESS server.

    I create a new Quick Report, select Ad hoc using named connection string. Then select Custom SQL Select...leaving as Portable... and then clicking on Query Builder.
    I then select 3 tables.
    I then choose the columns I need from the 3 tables.
    I then click on OK and then setup 3 arguments.
    Then go back to Query Builder.
    Goto Filter tab and add 3 lines for my arguments
    I then add 2 to Orders.
    I then click on Execute Query and everything works as expected.

    SQL query generated:
    Code:
    SELECT Project_List.ProjectID, Project_List.LPEJobNumber, Project_List.NewJobNumber, Project_List.V_WBS1, Project_List.ProjectName, Project_List.Closed, Wells.PrintOrder, Wells.Well, Wells.Diameter, Wells.ScreenTop, Wells.TD, Wells.sg, Wells_GwGauging.Date, Wells_GwGauging.DTW, Wells_GwGauging.DTP 
FROM [Project List] Project_List
	 INNER JOIN (Wells Wells
		 INNER JOIN Wells_GwGauging Wells_GwGauging
			 ON  Wells.WellID = Wells_GwGauging.WellID )
		 ON  Project_List.ProjectID = Wells.LPEJobNumber  
WHERE Project_List.V_WBS1 = :WBS1  AND  Wells.PrintOrder < 900  AND Wells_GwGauging.Date BETWEEN :first_date AND :last_date  
ORDER BY Wells.PrintOrder, Wells_GwGauging.Date
    I click on OK and then Finish and I am prompted for my 3 arguments, then the Quick Report Genie opens up.

    I select columns, groups, and then click on Preview.
    I then save the report.
    I can then double click on the report and view report.

    Up until this point, everything is going as planned.
    I can go back in and view the Edit Datasource Definition and everything looks OK.

    I can go in and change something simple in the report design and the SQL will change. In some cases, it seems to revert back to the very first SQL statement that generated. I haven't quite figured out what triggers this change, but it has happened 3 different times.

    Am I doing something wrong, or don't understand A5, or is this a bug?

    Thanks,
    Doug
    Tags: None
    #2
    Re: Quick Report and SQL query problem

    I haven't seen that happen before. Do you have default values in your arguments? Have you tried refreshing the data source from within the report when in design mode?

    Comment

      #3
      Re: Quick Report and SQL query problem

      My 3 arguments do not have default values. I'm not sure how to force it to refresh from the data source when in genie design mode.

      I have seen it remove fields from the select stmt and remove part of the filters I have created when I go back and check the SQL in edit datasource definition.

      Comment

        #4
        Editing Report Design Causes Changes to SQL DataSource to be Lost

        Steps to reproduce:

        1. Create a new report with an ad-hoc DataSource.
        2. After defining the DataSource, click 'Finish'; report designer opens.
        3. Edit the report layout and save it.
        4. Modify the DataSource to include additional columns, click 'Finish'.
        5. Right-click report and choose 'SQL DataSource > Preview records in DataSource...'; original and new columns are displayed (OK).
        6. Select report and click 'Design'.
        7. Add new columns to report layout.
        8. Do one of the following:
        8a. Click 'Preview' tab; no data appear in new columns (not OK). Exit the report designer without saving.
        OR
        8b. Re-save the report.
        9. Right-click report and choose 'SQL DataSource > Preview records in DataSource...'; only the original columns are displayed (not OK).

        Conclusion: Previewing a report design OR saving a report design causes changes to SQL DataSource to be lost.

        Workaround: Make the changes to the SQL DataSource again but do not then re-design the report.

        Comment

          #5
          Re: Quick Report and SQL query problem

          Maybe I'm missing something because I'm new to A5, but the workaround doesn't seem very viable. I'm not sure what to do after your step 5 if I need to add the new fields to the report.

          Comment

            #6
            Agreed: Not a good workaround

            It's not a good workaround but it appears to be the only one until the problem is fixed. So to add fields to a report you must:
            1. Edit the DataSource to add the new fields.
            2. Edit the report design to include the new fields (you will see the fields on the Columns tab but not their values on the Preview tab).
            3. Re-end the DataSource to add the new fields again.

            Comment

            Previous template Next
            Working...
            X