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 Memo Fields and dbt files

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

  • Converting Memo Fields and dbt files

    I was wandering if someone could point me to information about how to bring over my dbt (memo fields) over from Alpha4v6 to Alpha5v6?

  • #2
    RE: Converting Memo Fields and dbt files

    Jimmy

    It can be as simple as copying the dbf and dbt to your A5 database folder, adding the table to the A5 database, and making a structure change to that table.

    The conversion is automatic.

    Or use the convert_a4_to_a5() function.

    Please keep the A5 data files in a directory that is different than the A4 data files.
    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.

    Comment


    • #3
      RE: Converting Memo Fields and dbt files

      Just wanted to say thank you. It did the trick so far. Thanks for taking the time to help me :).

      Comment


      • #4
        RE: Converting Memo Fields and dbt files

        Which trick did you use? ;-)

        The change structure or the function?
        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.

        Comment


        • #5
          Re: Converting Memo Fields and dbt files

          I had come to the Forum to ask exactly the same question as Jimmy Dean except that I apparently need, at least, a little more direction than Jimmy. Following up on Al Buchholz suggestions - (1) could someone describe the needed structure change or (2) a little more information about the function that I was not able to find. I am assuming that the function will be used as a part of a copy operation. Alternately pointing me to the right spot in the instructions would be super. Thanks in advance for your help. Bob Moore

          Comment


          • #6
            Re: Converting Memo Fields and dbt files

            Bob

            For the structure change, make a new field, delete an existing field, or change the size of an existing field...

            Any change to the structure causes the memo field to convert.

            or use these functions listed in the interactive window... as needed... a5v7 - maybe others?
            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.

            Comment


            • #7
              Re: Converting Memo Fields and dbt files

              Since I didn’t mention it previously, I am upgrading from A4V6 to A5V7.

              First I want to thank Al Buchholz for his patience in providing assistance. Clearly I am missing something and need, at least, some more direction. When applying the structure editor to an A4 dbf file with a memo field I get the following error message, “The table/set is being used by another user or in another session and could not be opened in exclusive mode. Restructure can be viewed, but no change can be made.” After clicking past the error message and modifying the structure, I can only “save as.” On attempting to “save” it first repeats the first error message. On subsequent attempts it says, “Not an open table.” Using, “save as” the file structure is saved in an A5 format, but, no data is transferred. I could not get either copy nor append operations to move data from any A4 dbf file with a memo field to an equivalently structured A5 dbf table. Both of these operations work fine with A4 dbf files with no memo field.

              I should deeply appreciate the further directions I seem to need to transfer the A4 dbf file memo field data or being pointed to a book or documentation which provides these directions. On the book side I have thoroughly enjoyed using, for example, Learning Alpha5: the Data Base for Everyone, 2001, by Peter Wayne and would welcome purchasing another by him or other recommended author that would have the needed information.

              Comment


              • #8
                Re: Converting Memo Fields and dbt files

                Bob

                So you copied the A4 directory to a new A5 directory.

                Opened A5, made a new database in the A5 directory, added the A4 databases as A5 tables.

                You should then modify the structure of the table with A5 and not get the error message that the table is already open. If you get that message, we need to figure out why and fix it.
                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.

                Comment


                • #9
                  Re: Converting Memo Fields and dbt files

                  Again I want to thank Al Buchholz for his patience. To respond, if we mean the same thing by our words, I think the answer is yes. But to review: I copy an A4 dbf file and the associated dbt file (that carries the memo information in A4 applications) into a folder associated with one of my A5 applications. I then open the A5 application and using the “Add a Table/Set” command bring the A4 dbf file into the A5 application where I can interact with it. I can then bring up the structure editor where the error messages I cited earlier come up. It will let me “save as” after changing the structure and a new A5 table is created, however, without any data transfer. I cannot get either the “copy” nor the “append” operations to move the data to the new (but empty) A5 table since both at some point in setting up lead to the message that the A4 dbf file with a memo field “is not open.”

                  Incidentally, I can “open” the A4 dbt file with the memo information in either view or brows format. However, it will no allow running through records. In the view format, any attempt to change the record freezes the computer. This does confirm, however, that the memo data is there, just not in a way I have been able to transfer to an A5 table.

                  Comment


                  • #10
                    Re: Converting Memo Fields and dbt files

                    Bob

                    Can you send me a copy of the data? Something doesn't click here and having the data may answer the questions.

                    You can send it privately. Send me an email and I'll send instructions on what to do.

                    alb@bookwood.com
                    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.

                    Comment


                    • #11
                      Re: Converting Memo Fields and dbt files

                      As a follow up to this, here is what has happened.

                      Bob sent me an A4 table and I was able to convert it as previously described. Bob was unable to make the same steps work with the same table on his machine.

                      I connected with Bob's machine and verified the error, transferred the table to my machine and found the same error. This was the same table with the same size and datetimestamps as the other table that worked on my machine.

                      Nice....

                      I analyzed both tables with dsalvage and it noted errors in both (illegal data in some fields). Including the table that I was successful with. I've found that in other tables that have been slightly damaged over the years and have never been cleanup.

                      Bob then loaded A5 on the machine that had the original A4 tables and was able to convert all of the A4 tables to A5 (.dbt's became fpt's.) Other problems that he noted disappeared...

                      So exactly what was the problem? I'm not sure.
                      Suspects are:
                      1. damaged A4 tables.
                      2. transfer steps between computers.
                      3. Norton on the machine that won't convert properly.
                      4. Structure changes in A4 on a 32 bit machine with a version prior to a4v7?

                      At this point Bob is moving on since the data is restructured and working properly. Sometimes that happens.....

                      The swamp is drained and the alligators have moved somewhere else. And so have we.
                      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.

                      Comment


                      • #12
                        Re: Converting Memo Fields and dbt files

                        Again I want to thank Al for his support. It is people like him that make this forum so great.

                        Bob

                        Comment

                        Working...
                        X