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

Problem changing a field name

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

    Problem changing a field name

    I have a crosstab operation which produces a field with way more than 32 characters. This is causing a heck of a lot of problems.
    Because the field name is longer than 32 characters, I cannot use Xbasic to change the field name, and because I cannot change the field name, the report is not breaking correctly.

    Believe it or not, the field name that is produced is:
    production_dept_alltrim_str_recipe_no_padr_alltrim_item_30_portion_left_notes_20_

    I know, it looks impossible, but here is the screenshot proving it:
    long_field_name.png

    I have tried to use t.fieldname_change(), but to no avail, probably because of the long file name. I have tired grabbing on the first 32 characters of the file name and using that in the t.fieldname_change() function, but that did not work either.
    Any thoughts?
    Thanks,
    Jay
    Jay Talbott
    Lexington, KY


    #2
    Re: Problem changing a field name

    Hi Jay:

    I haven't done this in a while. Have you tried the following:

    Define the Crosstab again. In advanced, choose NOT to delete the data dictionary. Run it to make sure it's doing what you want, regardless of field name length.
    If it is, right click on the CrossTab and choose "Show Xbasic". Copy the xbasic into a script and edit the values (output name, fieldnames etc) to what you want, making sure not to allow the deletion of the data dictionary. Run.

    I think that should do it.
    Finian

    Comment


      #3
      Re: Problem changing a field name

      Thanks, Finian. I'll try it tomorrow morning and report back with the results.
      Jay
      Jay Talbott
      Lexington, KY

      Comment


        #4
        Re: Problem changing a field name

        I have tried to use t.fieldname_change(), but to no avail,
        I think you mean table.fieldname_change(). It's not clear from the documentation but you must specify the full drive-path-tablename-extension when using this.


        Code:
        t = table.open("aaa")
        flds_old = t.field_name_get()
        t.close()
        ? flds_old
        = a
        b
        c
        d
        
        flds_new = <<%nm%
        #abcdefghijklmnopqrstuvwzyz1234567890a
        #b
        #c
        #d
        #%nm%
        ? flds_new
        = abcdefghijklmnopqrstuvwzyz1234567890a
        b
        c
        d
        
        
        table.fieldname_change("p:\executive\mpurch\aaa.dbf",flds_old,flds_new)
        t = table.open("aaa")
        flds_old = t.field_name_get()
        t.close()
        ? flds_old
        = abcdefghijklmnopqrstuvwzyz1234567890a
        b
        c
        d
        flds_new = <<%ab%
        #z
        #y
        #x
        #w
        #%ab%
        
        table.fieldname_change("p:\executive\mpurch\aaa.dbf",flds_old,flds_new)
        t = table.open("aaa")
        flds = t.field_name_get()
        t.close()
        ? flds
        = z
        y
        x
        w
        Last edited by Stan Mathews; 08-06-2013, 10:08 AM.
        There can be only one.

        Comment


          #5
          Re: Problem changing a field name

          Stan,

          I did not know how to apply table.fieldname_change() until see this.
          Thank you

          Comment


            #6
            Re: Problem changing a field name

            You're welcome.

            If you are going to use this you should also be familiar with the somewhat inappropriately named TABLE.NAME_NORMALIZE().
            This method will help you avoid problems with field names that contain characters doesn't recommend. Also keep the field names at or under 32 characters.

            ? left(table.name_normalize("a long*field+name%with@some=garbage^characters"),32)
            = "a_long_field_name_with_some_garb"

            As you can see from the example above, table.fieldname_change() doesn't validate the field name list you supply.
            There can be only one.

            Comment


              #7
              Re: Problem changing a field name

              Jay

              Here is some code that I've used in this situation.

              It changes one fieldname to what I've chosen.

              Someday I'd like to expand it to do multiple fields with one table open.... Maybe next week.... Or I can find someone to do that..........

              Add this UDF to your database.
              Code:
              FUNCTION GET_FIELDNAME AS C (ptn as C, pfn as n )
              
              'Given a table name and field number return the field name
              '
              dim Key_fld_ptr as P
              dim t_source as P
              dim fld as P
              
              t_source = table.open(ptn)
              fld = t_source.field_get(pfn)
              
              get_fieldname=fld.name_get()
              t_source.close()
              END FUNCTION
              Crosstab xbasic is generated with this line...

              Code:
              'Add the table just created by the Crosstab operation to the Database..
              file_add_to_db(xtab_db_name)
              add this new code added at this point...
              Code:
              oldfieldname=get_fieldname(xtab_db_name,1)
              table.fieldname_change(xtab_db_name,Oldfieldname,"IndexKey")
              With a little mod of the last line it can be used on a summary operation also to made reasonable names..
              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


                #8
                Re: Problem changing a field name

                Thanks Finian, Stan and Al. It is working great now.
                Jay
                Jay Talbott
                Lexington, KY

                Comment


                  #9
                  Re: Problem changing a field name

                  You guys are doing something I never do. I never create or condone a field/index name of more than 10 letters, file names are no more than 8. Up to you though.

                  Comment


                    #10
                    Re: Problem changing a field name

                    Originally posted by amorris View Post
                    You guys are doing something I never do. I never create or condone a field/index name of more than 10 letters, file names are no more than 8. Up to you though.
                    Al

                    Nice name..

                    I agree, but in this case, the crosstab operation is creating the fieldname, not the developer. We're just cleaning it up..
                    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

                    Working...
                    X