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



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 field names

  • Filter
  • Time
  • Show
Clear All
new posts

  • Crosstab field names

    I have returned to an older program and encounter an old problem/nuisance. When I group rows by multiple variables I often have to use the ‘str’ or ‘substr’ operator. I have not found a way to get Alpha to create an simple field name that does not include the operator and the number of characters used.

    For example grouping on the first two digits of an ID code and the year portion of the date produces an field name for the crosstab something like “substr_ID_1_2_str_year_”.
    I would like to be able to easily assign a field name something like ID_Year

    Any suggestions on how to do this?


    PS The issue exists with summations and similar table operation methods

  • #2
    Re: Crosstab field names

    Hi Truman,

    I have not found that to be the case. Could you post a sample of your app for us to see exactly what is going on.
    Keith Hubert
    Alpha Guild Member
    KHDB Management Systems
    Skype = keith.hubert

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


    • #3
      Re: Crosstab field names

      The issue has been around as long as Alpha has and there is at least one thread in the Wishlist area.

      It is fairly easy to use Alpha's TABLE.FIELDNAME_CHANGE() to rename the fields to more friendly names.
      There can be only one.


      • #4
        Re: Crosstab field names

        Originally posted by Stan Mathews View Post
        The issue has been around as long as Alpha has and there is at least one thread in the Wishlist area.

        It is fairly easy to use Alpha's TABLE.FIELDNAME_CHANGE() to rename the fields to more friendly names.
        The thread that Stan mentioned something about Ver 10 truncating differently than Ver 9 and that made me check the two versions.

        Keith I find it a bit difficult to provide a sample app but I think that the following code and results will illustrate my problem.

        The following is the code I use to create the crosstab:

        <Start CODE>

        xtab_db_name = filename_decode("xtab unit_expenses.DBF")
        tbl ="expenses")

        ON ERROR GOTO ERROR25092005114742691

        filter = "expenses->L1_order = \"Expenses\" .and. between(Expenses->expdate,[varD->parameter1],[varD->parameter2])"

        crosstab.db = xtab_db_name
        crosstab.db_dd_delete = .F.
        crosstab.filter = replace_parameters(filter,local_variables())
        crosstab.row = "str(propid,8,0)+STR(UNITid,8,0)+c_year"
        crosstab.column = "L2_Order"
        crosstab.options = "I"
        crosstab.tabulate = "EXPENSE"
        crosstab.code = 1


        <End CODE>

        Using the same databse - ver 9 produces the following field name for the row grouping:

        - ver 10 produces the following field name for the row grouping:


        Technically this may not be considered to be a BUG but it renders apps created in earlier version not to function.

        Regarding renaming fields I believe that I once found a way, in one of the summation operations, to assign a field name -something like = “any name”. Unfortunately, as I recall you could not do the summation and name change at the same time. I think that you had to run the operation twice. It is going to take me some time to try and find my earlier example ( My programming is some time based on inspiration without the filling of useful examples.)

        I am not sure what my best approach is going to be to solve this problem. First I will have to find all the apps that have this problem. I know that I can use field rules that replace the row string but this could entail creating quite a few new fields: e.g., grouping for propid and unitid; propid and c_year….

        Any suggest greatly appreciated.