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

Converting data before import

  • Filter
  • Time
  • Show
Clear All
new posts

  • Converting data before import

    I am trying to import data from excel to A5 (exported to excel from another program). My main concern is the pk field. In Excel the values go like this: ar1...ar19...ar735, ...up to ar2731. I would like to import them as follows:
    ar1 becomes ar000001 in A5, ar19 becomes ar000019, ar2731 becomes ar002731, etc. In A5 the receiving field is currently empty awaiting the values from the import operation and is set in FR as an autoincrement starting with ar000001 (or should I start it with next highest value? --> ar2732). How should I proceed?

  • #2
    Re: Converting data before import

    You don't mention whether this is a one time procedure or not. If it is, then I would import into Alpha as is and create a new field that I would run an operation on to split the data, add the appropriate number of leading zeros to the second part and combine. Then export the relevant data to a final file format.


    • #3
      Re: Converting data before import

      Hi Doug: Thanks for your reply.
      Yes it will be a one time thing.
      [QUOTE=... I would run an operation on to split the data, add the appropriate number of leading zeros to the second part and combine.[/QUOTE]
      This is tricky part for me: how can I tell A5 to add 5 zeros to ar1...ar9, and only 2 zeros to ar2219?


      • #4
        Re: Converting data before import

        Being a one time thing, I agree with Doug to create a new field in which to convert the data into, but I would simply make the value of the new field a calculated field with this code (given the name of the field is pk as you wrote):
        left(pk,2)+ padl(substr(pk,3,7),6,"0")
        and then I would simply run the table utility Recalculate Calc Field (Field Rules) to populate the value into the new field. If need to get the values of the new field back to the original field, I would then make the original pk field a calculated field rule ="newfieldname" and rerun the table utility Recalculate Calc Field (Field Rules). Both the last two steps I would do AFTER backing up the imported table.
        Mike W
        "I rebel in at least small things to express to the world that I have not completely surrendered"


        • #5
          Re: Converting data before import

          Another quick way is to just do this in Excel before import using the following formula:


          This formula assumes that the data to alter is in cell A3 so adjust as necessary. Once you have pasted this to all the cells in your worksheet, do a quick "find" within Excel to look for arXXXXXX which would indicate a problem.



          • #6
            Re: Converting data before import

            Holly Cow Doug,
            That looks much, much easier.....not! :D
            Mike W
            "I rebel in at least small things to express to the world that I have not completely surrendered"


            • #7
              Re: Converting data before import

              Thanks guys, so much expertise and so helpful.
              I copypasted Doug's formula in Excel and works great.
              Thanks Mike for the padl(), I know that there is such function now.


              • #8
                Re: Converting data before import

                Excel has a nifty feature where you could drag couple of consecutive fields and create serial values.
                In the top cell enter ar00001, in the one below it put ar00002, highlight both and at the right lower hand corner drag the cross as far down as you want. You will have all the values you want.