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

Importing Tab delimited info

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

    Importing Tab delimited info

    I have had no luck using the import function to create and/or update a defined A5V8 dbf.

    Can anyone provide me with a link to a document or site that can provide help in doing this.

    I have used both the local and web "help" of Alpha and this has not resulted in a successful import.

    The spreadsheet import is working but the tab-delimited is not.

    This is a brand new purchase of A5V8 with all the current updates that I can find .. ..... HELP!

    tanx Don

    #2
    Re: Importing Tab delimited info

    Don

    Welcome to the Alpha world...

    Importing is one of the most fun parts of working with data. So many things can go wrong. ;)

    It's usually best to work in small steps and to add items/records as you go along.

    The number one issue that I run into with imports is data inconsistency. Characters where only numbers should be... Tabs within fields that result in mappings that are not expected...

    The next is illegal field names.

    It's really fun if you don't have control over the source. You can end up needing to do some 'tidy' work prior to an import.

    When I run into problems with importing a file, I start by dividing and conquering. Take a small sample file and make it work. Then add more fields to it, and finally start adding records to it.

    You can post a sample of the file here if you'd like. We can lend some advice...

    Remember ,in the case of imports especially, Alpha is a tool to use and there may not be a precise blue print for this particular job. It's driven by the limitations of the input file and the requirements of the output table.
    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


      #3
      Re: Importing Tab delimited info

      Al, thank you for the quick response.

      I clearly understand your comments re data integrity ... 30+ years in the information technology has scared me as well on this issue.

      I have spent a lot of time looking at the data (even at the hex level) to see if it is okay .. and based on what I know about A5V8 importing, it is okay .. the problem is that I am either misunderstanding what A5V8 needs or how to use the import tools .. that is why I am looking for a more descriptive explanation of this process.

      If you or anyone else can help with that, I would appreciate it.

      tanx again ... Don

      Comment


        #4
        Re: Importing Tab delimited info

        Don

        I'm not sure where to point other than the help file.. I think the latest videos are about the Alpha DAO import which doesn't apply here...

        I've attached a TAB delimited file that imported fine for me.

        Can you import this file into a new table?
        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


          #5
          Re: Importing Tab delimited info

          Al, thanks again .. I will look at the file and see what we can see ... tanx Don

          Comment


            #6
            Re: Importing Tab delimited info

            Al, thanks for the test file.

            It worked fine to import it into a blank dbf.

            However, what I need to do is import it into a database structure that is previously defined .. the reason is that the field sizes and location/seq of fields are not the same in the tab-delimited file as in the dbf file.

            Many other import functions with other software does this with no problem .. can A5V8 do this or do I have to use another process.

            Question I have are:
            - do the import fields have to be the exact size that the dbf is
            - when you get go to the "import" window thru the operations tab, what does the reference to "Field names:" indicate ....
            - "No fieldnames" - does this mean that there are no field names in the ascii file ... or what?
            - "Ignore fieldnames" - does this mean that there are field names in the ascii file .. just ignore them ???
            - "Use fieldnames" - does this mean that there are field names in the ascii file and use them to cross ref to field names in the dbf file ... or what???
            - can the ascii file have any extension (.txt, .csv, etc) or must it be ".asc"

            - when you are filling out the "Field name" in the table ... what is this doing ???
            - what is the significance of the sequence that the field names are in
            - what is the significance of the "Width" and "Dec" is this an ascii issue or dbf issue

            As well, are there limitations on the naming conventions for field names .. if so where could I find the explanation of what they are?

            Again if anyone can shed some light on this .. I would very much appreciate it.

            tanx for help ... Don

            Comment


              #7
              Re: Importing Tab delimited info

              ....are there limitations on the naming conventions for field names ?
              From the help file:
              Table and Field Names

              Alpha Five recommends that table names, field names, and paths to your files start with a letter (A-Z or a-z) and be composed of letters, numbers (0-9), and underscore (_) characters.

              Note : Do not use tilde "~" or "@" characters in table names, field names, and paths.
              Table and fieldnames that begin with numeric digits or other non-alpha symbols will lead to trouble.

              Comment


                #8
                Re: Importing Tab delimited info

                Originally posted by BEAMER View Post
                Question I have are:
                - do the import fields have to be the exact size that the dbf is
                No, but big enough to hold the data coming in...
                Originally posted by BEAMER View Post
                - "No fieldnames" - does this mean that there are no field names in the ascii file ... or what?
                - "Ignore fieldnames" - does this mean that there are field names in the ascii file .. just ignore them ???
                - "Use fieldnames" - does this mean that there are field names in the ascii file and use them to cross ref to field names in the dbf file ...
                - can the ascii file have any extension (.txt, .csv, etc) or must it be ".asc"
                Yes to all
                Originally posted by BEAMER View Post

                - when you are filling out the "Field name" in the table ... what is this doing ???
                - what is the significance of the sequence that the field names are in
                - what is the significance of the "Width" and "Dec" is this an ascii issue or dbf issue
                The data is loaded into a temporary table and then appended to the existing table, so you are describing the temp table....

                When the situation requires, I'll import into my own temp table, review the data, fix the data, and then append to the desired table.
                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