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

Report Help

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

  • Report Help

    Hi Everyone

    I'm lost (again...)

    I have a calculated field on a report based on a MySql table.

    I'm using sql_lookup in the field. In the expression builder the result works but in the report it only shows 8 characters.

    Ie: The field in the table has 12345678910 (which is displayed in the expression builder) but on the report it displays as: 12345678

    For the life of me I can't find where to change the display length properties of the field on the report as with normal fields.

    Can someone point me in the right direction.

    Regards,

  • #2
    Re: Report Help

    Update:

    Fixed but I'm not sure if this is the right way

    Copied the display properties from another field and applied it to the calculated field

    Can someone tell me if there is another way to change the display properties of a calculated field.


    Regards,

    Comment


    • #3
      Re: Report Help

      Field
      ..properties
      ....format
      .....field length - about the middle of the format tab
      Ted Giles
      Example Consulting - UK
      .

      sigpichttp://ec12.example-software.com//
      See our site for Alpha Support, Conversion and Upgrade.

      Comment


      • #4
        Re: Report Help

        Hi Ted

        Thanks for your reply

        Yeah I know that's where it's supposed to be be but this is what it looks like

        FormatTab.png

        Comment


        • #5
          Re: Report Help

          And it's not in one of the other tabs?
          If I recall correctly, a Calculated field has mixed up settings.
          Ted Giles
          Example Consulting - UK
          .

          sigpichttp://ec12.example-software.com//
          See our site for Alpha Support, Conversion and Upgrade.

          Comment


          • #6
            Re: Report Help

            Hi Ted

            No it's not. I've looked everywhere and can't find where to change the display width.
            I have other cal fields on the report which show the display width in the properties but not this one.
            Does it have to do with the sql_lookup used in the cal expression? I've never used it before so just asking.

            Strange how it shows correctly in the expression builder but not on the report.

            Comment


            • #7
              Re: Report Help

              Apologies Keith, I missed your last post.
              I will try and recreate the situation on my box.

              Edit.
              In your MySql table, set the value of the numeric field to BIGINT.
              This will give you 20 places to play with.
              You cannot change the table but you can look at the new field length in the Rules screen.
              Refresh the table definition in Alpha, then look at the field options again.
              When you test it, the field characteristics are not always re-set.
              Try entering a new long number - up to N 20.
              The Report should now take the long number.

              It is all to do with INT and BIGINT

              Hth.
              T
              Last edited by Ted Giles; 04-25-2019, 12:40 PM.
              Ted Giles
              Example Consulting - UK
              .

              sigpichttp://ec12.example-software.com//
              See our site for Alpha Support, Conversion and Upgrade.

              Comment


              • #8
                Re: Report Help

                Hi Ted

                Sorry for the delayed reply

                Thx for the input but I'm dealing with character data in the MYSQL field, varchar(80)

                Seems strange that when I use the sql_lookup function in a calculated field the display length isn't available in the format tab.

                FormatTab.png

                I solved the issue by coping the display width from another field and applying it to this field but I'd like to know if I did something wrong

                Regards,

                Comment


                • #9
                  Re: Report Help

                  Ok, so what does the code look like which populates the lookup character calculated field?
                  Ted Giles
                  Example Consulting - UK
                  .

                  sigpichttp://ec12.example-software.com//
                  See our site for Alpha Support, Conversion and Upgrade.

                  Comment


                  • #10
                    Re: Report Help

                    Here's the calc expression:

                    CalInvprime = SQLDATASOURCE->invprime
                    CalDesc = sql_lookup("::Name::llh","masterinv","invprime="+calc->CalInvprime,"[desc]")

                    invprime is INT(11) in the MYSQL table

                    In the expression builder the CalDesc result shows correctly but when on the report is only shows 8 characters.

                    Comment


                    • #11
                      Re: Report Help

                      Nope, cannot get it to fail using BIGINT as the invprime placeholder.

                      This is the usual construction of the lookup;

                      sql_lookup(connection,table,filter,result_expression,args)

                      From the Help Section
                      'In this example we pass in an open connection.
                      'Since the function will not have to open and then close the connection, it is significantly faster
                      dim cn as sql::connection
                      cn.open("::Name::Northwind")
                      table = "customers"
                      result_expression = "concatenate(city,' - ',contactname)"
                      filter = "customerid = 'bolid'"
                      ?sql_lookup(cn,table,filter,result_expression)
                      = "Madrid - Mart
                      Ted Giles
                      Example Consulting - UK
                      .

                      sigpichttp://ec12.example-software.com//
                      See our site for Alpha Support, Conversion and Upgrade.

                      Comment


                      • #12
                        Re: Report Help

                        Hi Ted,

                        Thx for the reply.

                        I'll try changing the MYSQL field to BIGINT.

                        Regards,

                        Comment

                        Working...
                        X