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

Importing memo fields from DBF to MYSQL ...

  • Filter
  • Time
  • Show
Clear All
new posts

  • Importing memo fields from DBF to MYSQL ...

    I have tried various ways to import tables that have memo fields. All the fields import except the DBF memo fields.

    I have used alpha's export - does not work with memo fields and is EXTREMELY SLOW

    I have used Navicat - inport dbf - not work for memo fields

    I have used Excel to open the DBF, then exported to text, then imported that text file via Navicat - again. does not work for memo fields.

    Is there something extra I need to do to make this happen?
    Gary S. Traub, Ph.D.

  • #2
    Re: Importing memo fields from DBF to MYSQL ...

    Not much experience with your issue. Have you tried the Workspace Upsize Genie under the Tools menu?

    Strike that thought, I was thinking you could choose which tables to upsize.

    I just tested an Alpha table with a memo field exported to csv and then imported to a MariaSQL table specifying the memo field be imported into a LONGTEXT field. seems to work, no idea about speed.
    Last edited by Stan Mathews; 05-30-2018, 04:21 PM.
    There can be only one.


    • #3
      Re: Importing memo fields from DBF to MYSQL ...

      Thanks for looking Stan. I will try exporting to csv. I already tried it via text, but at this point I would do a rain dance if it could help.
      Gary S. Traub, Ph.D.


      • #4
        Re: Importing memo fields from DBF to MYSQL ...

        I have, in the past, used Alpha's export feature to export dbf to MySql. ALL my memo fields, on this project or that, exported the memo fields successfully without incident.
        AlphaBase Solutions, LLC

        [email protected]


        • #5
          Re: Importing memo fields from DBF to MYSQL ...

          I am the same as Peter, had no problems


          • #6
            Re: Importing memo fields from DBF to MYSQL ...

            Yes, alpha's export does work but it is incredibly slow. One of my tables was still running after 5 hours. So I have been spending lots of time trying to look for a better solution. Navicat works fantastic for importing most of my tables, and does so in a very small fraction of the time that the export operation takes.
            Gary S. Traub, Ph.D.


            • #7
              Re: Importing memo fields from DBF to MYSQL ...

              Google FPT converter. Your memo fields are in FPT format so that is why it's taking time.
              Convert as you wish and then import the content.
              See our Hybrid Option here;


              • #8
                Re: Importing memo fields from DBF to MYSQL ...


                Longtime ago we used a program called spectral core Full convert to automate conversion of our paradox tables to mysql.
                Paradox has the same problems with memo files as dbase. But for spectral core it was no problem at all.




                • #9
                  Re: Importing memo fields from DBF to MYSQL ...

                  Thanks for all the suggestions. I am now working with a SQL consultant, and am making some progress. Turns out that using AlphaDAO for a very large table (many, many memo fields) and approx 165,000 records was taking hours and hours so was essentially useless to me because this is not a one time thing for me - I will need to do many times. However, using alpha's export to text (or csv) takes just 35 to 40 seconds, and then using Navicat to import that text file into the pre-exisiting sql table (with all the correct field types pre-defined) takes just another 4 minutes! The first step was using ALphaDao to export just one record so that alpha created the sql table with all the correct fields, field types, and lengths, etc. Then delete that one record, and do as I described above - if you skip this step, and then import the text file, the sql table ends up with all fields being VARCHAR (255) which is not what we want.

                  One problem though - importing the data with navicat in this way leads to many errors, e.g., mostly data too long for field and funky characters perhaps from users having copied and pasted from word in to a memo field for example. Turning strict mode off for the import eliminates all those errors which is great - got this suggestion from a google search - but I worry some what effect this could have. Perusal of the resulting table looks ok, but there is far too much data to be sure. So I am wondering what others think about this, or any experience with turnig strict mode off for this purpose.
                  Gary S. Traub, Ph.D.


                  • #10
                    Re: Importing memo fields from DBF to MYSQL ...

                    I've posted this Navicat issue on the RAD group Gary. A lot of guys ues it there.
                    See our Hybrid Option here;


                    • #11
                      Re: Importing memo fields from DBF to MYSQL ...

                      Hi Ted,

                      I would love to see that. Where is the RAD group?
                      Gary S. Traub, Ph.D.


                      • #12
                        Re: Importing memo fields from DBF to MYSQL ...

                        Try this Gary.


                        One of the SQL DBA's suggested it after concluding that Navicat was unsuitable.

                        As for the RAD group, we are not a public group and evaluate all sorts of RAD software so it's not dedicated Alpha, although there are several who use Alpha DT and Web.
                        See our Hybrid Option here;