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

ODBC Import Genie

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

    ODBC Import Genie

    I've been evaluating A5V5 for the past couple of days and I am having problems importing an Access 2000 database. The error I get is:

    Field will not fit in record. Error occurred @ line 3580. This happens on about 5 tables up to this point. When I select the OK button, it restarts the import from the beginning and gives the same error again. I was actually hopint I could convert my Access tables with little or no intervention, but this error message has me really confused. Does the import actually function correctly, or am I just spitting in the wind?

    The ability of the Import Genie to import my Access tables will critically impact the decision for our company to switch from Access to A5V5, so it's pretty important that this post be answered quickly, before my trial period expires.

    Thanks in advance for your assistance!
    Tags: None
    #2
    RE: ODBC Import Genie

    Joseph

    I've noticed that Access character fields tend to be 255 characters when that may not be needed. Too many of those can exceed the record size of dbase.

    I've had a similar problem putting Oracle tables into Access. Access also has a limit, but it's probably a little higher than dbase.

    Your options are to make the record lengths smaller by either making the fields a reasonable size, breaking the table into multiple tables, or eliminating unneeded fields.

    Or a little of each.

    That's also why only some tables have a problem. The other tables are probably shorter in length.

    It's all part of the fun of data conversion. :-)

    (and it doesn't matter what the source or target of the data is - there's always something to account for)
    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: ODBC Import Genie

      None of the fields of my tables are longer than 250 characters in length. However, I do have some memo fields that are unlimited and could easily go over that plateau. How does DBase handle the memo fields? I thought (from previous experience with DBase) that the memo fields were unlimited also.

      Thanks for your post!

      Comment

        #4
        RE: ODBC Import Genie

        Joseph

        Hope I can help.

        It's a question of how many fields or how many bytes the total length of the record is. Memo fields should only count about 10 bytes, since that is the size of the pointer in the data table.

        If you exceed the total byte limit for a record, you'll probably get this error.

        I doubt that the memo fields are the problem. They should convert just fine.

        You might try creating an access query that has 10 fields (include a memo field too or not to eliminate issues) from a troubled table and import the query. As I remember, you can import from a query in the ODBC genie. Otherwise just make an access table with the 10 fields and import that.

        That should help confirm the theory that it's the record byte length that is exceeded.

        Let us know how it works!
        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
          ODBC Import Genie

          Joseph:

          I haven�t imported an Access database into A5 for more than 2 years. However, if memory serves me correctly, I also had an import problem that was related to the Memo fields. Access 2000 uses a different format than Alpha Five, which are FPT files. When I changed the Access Memo fields to text fields, the import worked smoothly.

          I don't know if that is your problem because you're receiving a different type of error message. But changing your memo fields to text fields or temporarily removing them during the import procedure might be worth a try

          Robert

          Comment

            #6
            RE: ODBC Import Genie

            Do you mean it halts at record #3580? If so, you might look at that record for special characters that could be interpereted as delimiters.

            Comment

              #7
              RE: ODBC Import Genie

              No, it doesn't stop at record 3580, it stops at line 3580 in the import program.

              My memo fields are never as short as a text field, due to the fact that they contain the description of the machine that is represented by the record. I have actually had machine descriptions take 3000 characters because they sometimes give specifications of the particular machine. For example, a machine may have "6 1-1/4 inch spindles, with a fluted mounting rim with each rim having 3 surfaces to mount separate belts..." etc. etc. That would be one part of a machine that could have 50 parts like that.

              ...just so you get an idea of what I'm working with.

              Comment

                #8
                RE: ODBC Import Genie

                The dbase file format has a finite record length (something like 4000 characters in field length) which you are probably exceeding. Base your import on a few of the fields and see if it works. Unfortunately we are limited by the finite dbase file format record length when doing imports using the ODBC import genie. One way around this is to do two imports with half of the first first fields in the Access table (including a unique primary key) in the first import and the second half in the second import (again with the unique primary key). Then you will need to merge the files in A5.

                Comment

                Previous template Next
                Working...
                X