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

Crosstab Query - Incorrect Field Type

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

    Crosstab Query - Incorrect Field Type

    Hi. I've created a crosstab query, however the record value which is set as Group by Row is setting the field type to Character in the result table: rather than the actual field type of Numeric.

    This is then causing problems with linking, when i'm creating say links for mapped tables etc.

    Can anyone advise me on how to fix this, please. Many thanks in advance
    Tags: None
    #2
    Re: Crosstab Query - Incorrect Field Type

    Hi Mustafa,

    Welcome to Alpha.

    If this field is not used for any math calculation then it is best that it is not numeric to start with.

    I'm assuming it is a Id field. You can always use it as an expression to link to other tables with the VAL() function.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment

      #3
      Re: Crosstab Query - Incorrect Field Type

      Thanks Keith for the speedy response! I'm new to Alpha (love the product and getting to know it). I'm used to mainly working with Access, but making the transition. To be honest, my skill level in coding etc is at a basic level.

      You're right the field is an ID (Primary Key) field which is set at Numeric Type. I'm not confident yet to 'play' too much with coding/expression. I've got a database from Access which i'm migrating into Alpha. The tables etc are set and linked.

      Rather than having to change the field type and then following it all the way through to the other tables, which I may have to do if no other way. I would prefer however just being able to make sure the field in the Crosstab Query comes out as it's meant to.

      Is there a simple way to make this happen, as I'd want to make sure the process is as automated as possible. The output from the Crosstab query will 'feed' into a mapped table for the final output. This will be an automated (press of a button) process with the finished product.

      Thank you.

      Comment

        #4
        Re: Crosstab Query - Incorrect Field Type

        Hi Mustafa,

        I understand what you are trying to do after you have created the crosstab table but after thinking about it, I'm not sure what you are trying to do is correct.

        The idea of the Crosstab is to have a table of data to use in a report the same as a Pivot table in Excel.

        There is no reason why a crosstab table cant be used in a set linked to other tables, it just sounds a little strange to me.

        Could we have some sample data and a full explanation of what you want as the end result.
        Regards
        Keith Hubert
        Alpha Guild Member
        London.
        KHDB Management Systems
        Skype = keith.hubert


        For your day-to-day Needs, you Need an Alpha Database!

        Comment

          #5
          Re: Crosstab Query - Incorrect Field Type

          Originally posted by mustafasheikh View Post
          Hi. I've created a crosstab query, however the record value which is set as Group by Row is setting the field type to Character in the result table: rather than the actual field type of Numeric.

          This is then causing problems with linking, when i'm creating say links for mapped tables etc.

          Can anyone advise me on how to fix this, please. Many thanks in advance
          You can link with an expression

          val(<CharField> will link to a numeric field

          or str(<NumericField>,<strlength>) will link to a character field - be sure the expression is the same length
          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

            #6
            Re: Crosstab Query - Incorrect Field Type

            Dear Keith. I've solved the problem, by taking your earlier advice on changing the value type, but rather used the STR() function instead.

            I was trying to create a browse with certain fields showing as columns. I needed the crosstab query to do the first stage formatting/structuring' of the layout/data. The crosstab created the output table, which I then used to link to the necessary mapped table. Finally used a browse to output the data in the visual format that I needed it in.

            I was encountering the problem at the crosstab query stage, where at the output table the value (field-type) was changing from the native Numeric to Character. This then caused errors when I tried to link the out-put table to the mapped table, as the two linking field types were incompatible.

            What I did, to keep things simple, was to create a calculated field (dummy linking field based on the primary-key) at the original table. This automatically took the value of the primary key (set to Numeric field type) but this time the field type is set-up to change to Character (using the STR() function. I'm then using this dummy_id field for the crosstab query and it works a treat. Thanks for your hint on lateral thinking. Cheers.

            Dear Al. Thanks for your advice also.

            Comment

            Previous template Next
            Working...
            X