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

Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

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

  • Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

    I beleive I encountered a bug when using the the "xxxxxx"$Status, Order, & Conditional Combo within an Action Script using a Button's "OnPush". I'm not sure how to get this to Alpha's tech support's "Bug" department and thought I'd post it here and someomr could eithrt forward it to teck support or guide me on how to submit it.

    While "xxxxxx"$Status works, it will not sequence the Report output. I tried deleting the Action Script, Tr-building the Indexes of the table and re-building the Action Script. The same thing happens ecevy time. I get the right selection, but no sort.

    On Push Statements follow:
    1) "ON Push" - Preview a Layout is selected.
    2) Report is Selected
    - RenterResLastName is the Report selected
    - Display "Print/Preview" prompt at Runtime is selected.
    3) Select Records to Print
    - Record selection by a Filter Expresssion is selected
    4) Filter Expression
    - "Renter"$Status
    5) Order Expression
    - Lastname

    Note: I have Label's and Report Buttons with the exact same syntax as described above and they work just fine. I spent a many hours trying to figure out what I did wrong, if anything, however I do not see any error on my part.

    Richard or Selwyn, I know you browse the board so perhaps you can respond to this potential bug. I'd gladly send you my app for your review.

    Thanks,
    Rudy Pataky

  • #2
    Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

    Help menu - Send a bug report - follow the directions

    You could also post your app here to see if anyone can repeat your problem
    Last edited by Bill Griffin; 04-30-2008, 08:06 AM.
    Bill Griffin
    Parkell, Inc

    Comment


    • #3
      Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

      Thanks Bill.

      Comment


      • #4
        Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

        Rudy, if you attach a sample database with instructions for us to follow to see the issue you're having perhaps we can suggest a work around or fix it for you.

        -- tom

        Comment


        • #5
          Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

          Tom,

          Your very gracious however I sent sent Selwyn my daya base and he is going to take a look at it. I'll keep you posted on this. Being that I'm not an expert, not even close, it's probably something I did that I cannot see.

          Thanks again for the support,

          Rudy

          Comment


          • #6
            Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

            Hi Tom,
            Can you run an application on a couple of computers that are not networked? Application on one and the others attachs to them somehow with a cable?

            Thanks

            Comment


            • #7
              Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

              What I meant to say was without a File Server. I did some research and I can Direct Connect 2 computers with Crossover Cables. Forget the previous message.

              Comment


              • #8
                Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

                Originally posted by Rudy16 View Post
                I beleive I encountered a bug when using the the "xxxxxx"$Status, Order, & Conditional Combo within an Action Script using a Button's "OnPush". I'm not sure how to get this to Alpha's tech support's "Bug" department and thought I'd post it here and someomr could eithrt forward it to teck support or guide me on how to submit it.

                While "xxxxxx"$Status works, it will not sequence the Report output. I tried deleting the Action Script, Tr-building the Indexes of the table and re-building the Action Script. The same thing happens ecevy time. I get the right selection, but no sort.

                On Push Statements follow:
                1) "ON Push" - Preview a Layout is selected.
                2) Report is Selected
                - RenterResLastName is the Report selected
                - Display "Print/Preview" prompt at Runtime is selected.
                3) Select Records to Print
                - Record selection by a Filter Expresssion is selected
                4) Filter Expression
                - "Renter"$Status
                5) Order Expression
                - Lastname

                Note: I have Label's and Report Buttons with the exact same syntax as described above and they work just fine. I spent a many hours trying to figure out what I did wrong, if anything, however I do not see any error on my part.

                Richard or Selwyn, I know you browse the board so perhaps you can respond to this potential bug. I'd gladly send you my app for your review.

                Thanks,
                Rudy Pataky
                i sent you a reply by email a few days ago. perhaps you should check your spam folder.

                there is no bug.

                you have defined a report and in the report definition, you have specified 'street address' (i forget the exact field name you used, but its not important) as the report order.

                then, in your xbasic you have something like this

                query.order = "lasname"
                query.filter = "some filter expression - not important what"

                report.print("reportname",query.filter,query.lastname)

                and then you are expecting to see the report ordered by lastname.

                that's not is what's going to happen.

                the order that you specify at runtime ("lastname") is an INCREMENTAL order.

                so the report will be sorted by 'street address' and then any records that have the same street address will be sorted by 'lastname'

                if you want to specify the complete order expression at runtime, just remove the order you have defined as part of the report definition.

                Comment


                • #9
                  Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

                  Hey Tom,

                  The only bug that surfaced was me. Sllwyn pointed that out to me. There was an order statement in the report and then another in the "On Push" of a Button. All I had to do was remove the Order Statement from the report and all was fine. I looked for a long time and did not catch the error.

                  Comment


                  • #10
                    Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

                    This is why it's often best to post examples here first. If Selwyn checked every script that somebody thought might be a bug he wouldn't have time to do them all and future A5 development might come to a halt. If people on this message board can't fix the problem, then it's probably worth submitting a bug report.

                    Those of us who've been doing this for years would probably have caught this one right away if we had a sample. I've learned through the school of hard knocks - if the sort order or filter for a report doesn't seem to work, check the settings in the detail section and review the Group settings. The issue with your description, and it's a common issue, is that it really didn't include the full story because you probably weren't even sure what the full story was. And don't take that wrong, we all do it. We get ourselves in a rut and forget a key factor somewhere else even when we should know better. I often talk with another developer when I run into problems and most of the time it turns out I forgot something critical in the first explanation - often that "something forgotten" is the key to the whole problem.

                    Comment


                    • #11
                      Re: Potential Bug using "xxxxxx"$Status & Order & Conditional Statements

                      You are right on Cal. Lesson learned.

                      Comment

                      Working...
                      X