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

Memo problem

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

    Memo problem

    Hi,

    I am having a memo problem. I'm not sure if if is due to corruption or not. It involves a *.DBT file originally created in A4. My original application was created in A4 about 10 years ago and is still in use. When recreating my application in A5 (originally in A5V4.5, then Ver.5), I just zipped up the files from the one computer that it is used on and unzipped it to my development computer. (Yes, I know I should have only copied the *.dbf and*.dbt files and not the application files, but that is what I did). I am using the latest build 1431_1038.

    After a lot of development, I deleted all the records from the tables and packed them (last October). For testing, I began anew with my recreated application and have entered a small group of records (113 records now in the parent table). There is a child table with a memo field which is linked one-to-one with the parent table. This child table is named Znote.dbf. From what I can tell, A5V5 is still using my Znote.DBT file for storing memos. I see an associated Znote.FPT file, but the database is not using it. The reason I know this is because, if I rename the Znote.DBT to something else and try to open the database, I get the error message "Unable to find or locate memo file." If I do the converse and leave the Znote.dbt name intact, but change the Znote.FPT file name to something else, I have no problem opening the database. Unfortunately, my memos are incorrectly linked to the child records or in some cases totally missing. I am not sure exactly when the problem started, as I have not audited the memo fields for correct information previously. Going back to printed reports, I see evidence that the problem goes back more than a month. It may have been going on all along. By the way, the Znote.dbt file size if about 15KB.

    Any suggestions on how to sort out this mess? I tried restoring the database from my backups, but they all seem to have the same problem. Should I just rename the Znote.dbf table, delete the Znote.dbt file and append the child records (minus the memos) to a newly created Znote.dbf table and re-enter the memo fields from the paper reports I have been keeping? I tried restoring the database from my backups, but they all seem to have the same problem.

    Any help would be greatly appreciated.

    Thanks,
    Robin Sculthorpe

    #2
    RE: Memo problem

    Robin

    Try duplicating the table and see if the duplicate uses just the fpt file. If it does, delete the original and duplicate the copy using the original name.

    Sometimes just opening the table structure and resaving might work.

    Jerry

    Comment


      #3
      RE: Memo problem

      Jerry,

      Your idea sounds much simpler than mine, but I already started plowing through this problem in my own fashion. I had to do some minor repairs because of the broken link between the parent and the child, but so far everything seems to be working OK. I have one more relatively simple form to rebuild that was based on the child database (Znote.dbf). I will be extensively checking the memo fields for a while and religiously doing backups, packs, and compacts. If all goes well, I will follow up on this thread as it might be useful to some other folks who have been experiencing memo field problems (especially, if they utilized *.dbt files from another database program).

      It would be nice to have a better understanding of why a *.fpt file showed up in my application, but was being ignored for the most part while the *.dbt file was still being utilized.

      Thanks for your input.

      Robin Sculthorpe

      Comment

      Working...
      X