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

Converting Paradox memo fields

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

    Converting Paradox memo fields


    There was a posting back in December 2003 (Brad Porter)regarding a memo field that would NOT convert for use in A5V5. I have run into the same problem and I have also stumbled onto a solution.

    I am in the process of converting my data files and application from Paradox 4.5 (for DOS) into A5V5 and was using the export utility in Paradox to create dBase IV files (that is the latest file version offered by this old version of Paradox).

    The memo field in the exported DBF files was garbage. However, when I changed the export format back to dBase III, the DBF memo field was 100% intact when viewed in A5V5.

    Can anyone tell me if A5V5 will have any problems with the older dBase file format???
    Bruce Cavenaile

    #2
    RE: Converting Paradox memo fields

    Bruce

    I've usually found that a5v5 will convert the format, if not right away, at least when a structural change is made.

    See if it has done that, other wise make a minor change and see what happens. (backup backup backup.....)
    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: Converting Paradox memo fields


      Al

      I just tried "Edit Structure" on a few of my larger tables and no error messages resulted so it looks like I'll be o.k. using the older dBase file format.

      I'm still using my Paradox application as my production system while I'm getting acquainted with A5V5. When I'm finally ready to sever my Paradox umbilical cord I'll make sure to carry out a restructure for every table in addition to re-building the indexes as has already been suggested.

      Bruce
      Bruce Cavenaile

      Comment


        #4
        RE: Converting Paradox memo fields

        Bruce

        I'd look to see if the files were modified by looking at the windows datetimestamp.

        I'd also do a report or operation that reads all the records. Might be a good place to open the field rules and re evaluate field rules to see if anything invalid comes up. Like unexpected values - characters in numeric fields.....


        Also I won't move any files back and forth between Alpha 5 and my production Paradox. One way is enough work, let alone both ways.

        Do you have any memo fields in Paradox? Is the file extension .fpt or something else?

        Just items to watch.

        Sounds like fun!
        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: Converting Paradox memo fields

          Writing just a little fast today.

          Memo fields.. duh

          What is the extension that paradox uses?
          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


            #6
            RE: Converting Paradox memo fields


            Al

            This version of Paradox carries the memo field in a separate file with a matching table name and extension of .MB which is then exported to a .DBT file.

            Once I get a little further into this process I will be able to check on any impact to the field rules, layouts, etc before making my final leap out of Paradox, e.g. if some problems appear I can still do a fresh export in dBase IV format for all tables EXCEPT the one or two that have memo fields and send those over in dBase III format.

            I am going VERY slowly at this because I want to be fully comfortable in A5V5 with a functional application BEFORE I trashcan the Paradox program.

            Bruce
            Bruce Cavenaile

            Comment

            Working...
            X