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

Moving dbf to MySQL including memo fields

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

    Moving dbf to MySQL including memo fields

    If so, what field type did you choose for the memo field in mysql? Would you mind sharing the initial steps within alpha you took to get this done?

    George
    Tags: None
    #2
    Re: Moving dbf to MySQL including memo fields

    Use longtext for the MySql field type.

    To handle the conversion you create an export operation in Alpha. Use the Genie to set it up the way you want. Alpha will set the field types for you.

    There are lots of things to be aware of if you are planning on using your existing application with the new SQL backend.

    Read up on the Database Upsize Genie feature pack add on for some caveats and things to be aware of. (removed broken link)​ You don't really need the Upsize add on, but expect to spend quite a bit of time on the conversion if your app is of any size. I only had the one app to convert and so I did not buy the add on.
    Last edited by Lenny Forziati; 06-02-2023, 01:26 PM. Reason: removed broken link
    Jim Coltz
    Alpha Custom Database Solutions, LLC
    A5CustomSolutions.com
    [email protected]

    Comment

      #3
      Re: Moving dbf to MySQL including memo fields

      Thanks Jim.

      Comment

        #4
        Re: Moving dbf to MySQL including memo fields

        One thing to be aware of: in MySQL, autoincrement fields are all integer fields. You may have to change field types if you created character-based autoincrement fields in Alpha Five.
        If your memos are not that large, regular text fields in MySQL hold up to 65536 characters -- roughly 25-30 pages of text. I use regular text fields for memos unless I am storing images or scanned pdfs. Then I use longblobs.

        Comment

          #5
          Re: Moving dbf to MySQL including memo fields

          Thanks Peter, this is a application for a collections department and they input quite lengthy notes. Due to the nature of the record detail in this app, I have several memo type fields. When A5 v10 opens, it takes a rather long time to get the app started. New PC, load time around 1-1.5 minutes. Not special code loading at startup. Thinking that maybe MySQL would help to resolve this.

          Comment

            #6
            Re: Moving dbf to MySQL including memo fields

            Hi George.
            That's a very long load time and raises a question about the design of your application. Are you pulling many large memo fields over at once into a browse onyour main form? Do you have a complex set on your main form? Do you have calculated fields that are time-consuming to calculate, e.g., including tablesum() or dbsum()?
            If it's just the initial application load, it doesn't really matter in the course of a workday, but if you have that delay every time you come back to that form, then you have a design issue. It's not clear that will be made any better by MySQL. MySQL has many advantages over native dbf but native dbf tables are quite snappy enough for small networks (10-20 users).

            Comment

              #7
              Re: Moving dbf to MySQL including memo fields

              I do have about 7 dbsum's going on and the view has 4 tabs that each have memo fields for the notes regarding the record. I believe that it is more on the design side.

              Comment

                #8
                Re: Moving dbf to MySQL including memo fields

                "Simplify your Application for Better Performance" is a useful article. It's online at www.learn alpha.com

                Comment

                Previous template Next
                Working...
                X