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

Drilldown in layout table report

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

    Drilldown in layout table report

    Is this possible? I don't see an event structure for a cell in a layout table report.

    As in a free form report, I need a cell click event to fire some xbasic. Converting a free form report with drilldown to lt, I don't find the event anywhere in the lt version.

    Bill.

    #2
    Re: Drilldown in layout table report

    On some of my reports, I have placed hotspots with onPush events that link to other screens. As a part of the onPush event, I closed the report when I opened the screen.

    -- Dick James

    Comment


      #3
      Re: Drilldown in layout table report

      In a layout table report? Hotspots are a toolbox item only available in free form reports.

      Comment


        #4
        Re: Drilldown in layout table report

        Sorry about that. The layout table reports are new with Version 11 & the Alphapedia implies that they are useful for web reports. Since this thread is for desktop applications, I assumed you were using a conventional report. My error. I have not used the layout table reports.

        Comment


          #5
          Re: Drilldown in layout table report

          One advantage of layout table reports for desktop is that they preserve the layout when saving a report as Excel. Free form can really garble things when saving as Excel.

          One downside is that it appears they have not been widely used.

          Bill.

          Comment


            #6
            Re: Drilldown in layout table report

            Originally posted by Bill Parker View Post

            One downside is that it appears they have not been widely used.

            Bill.
            We are waiting for you to lead us....
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment


              #7
              Re: Drilldown in layout table report

              It would be great if someone who uses these reports in the desktop WOULD take the lead and show us how to use them! Like how do you get an imported browse to have a line around it? If the genie didn't dump it into the subreport footer section, I could at least add a line at the bottom...
              Robin

              Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

              Comment


                #8
                Re: Drilldown in layout table report

                Everything in a LT report is in a "cell". And each cell has border properties that can be turned on. Bring up the Properties dialog from Task List -> Properties. Is that what you are talking about?

                Comment


                  #9
                  Re: Drilldown in layout table report

                  I think so. For the subreport header fields that worked pretty well, but in the footer where the browse is, all I get is double lines since a bottom border applies to every row. I tried to overlay a frame but it needs to be a fixed size and that threw it onto a 2nd page.
                  Robin

                  Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                  Comment


                    #10
                    Re: Drilldown in layout table report

                    Are you saying that in a freeform report with an embedded subreport, that the subreport converted to layout table? I just tested one and it did not convert the subreport. LT reports want you to create a second LT report and link into a cell(s) it as the subreport.

                    At first I resisted creating LT reports from scratch, but it saves heartache if you do it. Otherwise, try to get the free form report objects lined up like html cells as much as possible. If you convert FF reports, you can use Reports -> Check for overlapping controls before hand. Conditional objects do not convert well to LT, and will report as overlapping controls. After converting a FF report, you will likely want Arrange -> Automerge to reduce the row clutter.

                    LT reports are like Forest Gump and a box of chocolates... But nice when you get it done.

                    Bill.

                    Comment


                      #11
                      Re: Drilldown in layout table report

                      Since I have your attention - can you tell me what the difference is in properties for the OBJECT vs properties for the CELL? They appear to be the same properties, but what is the object?

                      thanks,
                      Robin

                      Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                      Comment


                        #12
                        Re: Drilldown in layout table report

                        Object -> Properties is used for freeform reports, since that report type is a collection of objects. Same as right click on object, Properties. I never use that for LT reports, which is a collection of cells. For LT, use TaskList -> Properties. That dialog can be used for freeform reports also, but I tend to use the older version for freeform.

                        Comment


                          #13
                          Re: Drilldown in layout table report

                          One nice thing about LT reports that I just used... An entire row can be suppressed based on an expression. This can be done somewhat with conditional objects in freeform, but it is much more cumbersome.

                          Comment

                          Working...
                          X