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

Error Locking

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

  • Tim Sutherland
    replied
    Re: Error Locking

    I've run into this a few times and here's the only solution I've found.

    Work on a backed up copy of the database.
    If you have 200,000 records, run an operation and delete records 1-100,000.
    Compact the database and check the .fpt file size. If the file size is normal, work on a full copy again and this time delete records 1-50,000. Keep doing this until you narrow down the record with the corrupt memo field.

    Once you locate the record, delete it and your problem is solved without having to restore an outdated backup.

    This may take several hours to accomplish, but it will isolate the corrupt record.

    It's also critical to not allow users to use the database before this is repaired. I found that edits to another records memo field while there is a corrupt .fpt file will result in more corrupt records making this task much more difficult.
    Last edited by Tim Sutherland; 08-23-2016, 07:41 PM.

    Leave a comment:


  • Ted Giles
    replied
    Re: Error Locking

    Well maybe.
    Perhaps "belly up", or "down the tubes" would have done, but "Wahoonie" got you thinking.
    PM on its way.

    Leave a comment:


  • MoGrace
    replied
    Re: Error Locking

    Aha, so you are admitting you used the word incorrectly!

    Leave a comment:


  • Ted Giles
    replied
    Re: Error Locking

    [QUOTE=MoGrace;715866]wahoonie? Is that olde English?

    http://wiki.lspace.org/mediawiki/Wahoonie

    Leave a comment:


  • DaveM
    replied
    Re: Error Locking

    One sure way to cause a memo field to corrupt is to get it out of synch with the dbf.
    copy the fpt file out - add a few records to the old ftp/dbf and then copy the fpt back to the folder and overwrite the original one. 75% chance of corruption. Same with doing that with the dbf file.

    Just in case someone did not know.

    ftp files and dbf files need to be thought of as inseparable.

    Leave a comment:


  • draxx2755
    replied
    Re: Error Locking

    The memo field was the standard fpt table A5 creates. I like the idea of sending the memo date to an Excel or CSV file before it goes "wahoonie". I've more or less completed rebuilding the db now. Actually, I moved some 40,000 older records prior to exporting my main table data which helped with the size of the file in general. After exporting the data, and then importing the data into the new table, and then packing it, it recreated the fpt file and it is now at it's normal size. After that, it was just a matter of duplicating tables with records, indexes, etc to my new folder and then copying operations and code (scripts and functions) to the new folder. It now looks as if all is well. My larger concern is what actually caused it to go "wahoonie" in the first place. Probably will never know.

    Oh, and I forgot about A5Doc, thanks for the reminder. What I did do though was to copy and paste all field rules to a notepad file and then just copy and paste back into the appropriate fields. Faster then manually retyping all...lol, especially at my typing speed. Thanks again for all the input.

    Leave a comment:


  • MoGrace
    replied
    Re: Error Locking

    wahoonie? Is that olde English?

    Perhaps when he tries to export the data we will find out if the memo field is RTF, HTML or regular...

    Leave a comment:


  • Ted Giles
    replied
    Re: Error Locking

    I think Robin has a good test solution.
    Memo fields are a good but PITA when they get corrupt.
    Copying that much data out into a new Table ( don't forget Mr Backup) may isolate the problem
    I think a good few of us normalise memo fields separated from the working tables. Easier to back up.
    Suggest you send the memo data and source ID to an Excel or CSV so you can get it back if it goes wahoonie.

    Leave a comment:


  • MoGrace
    replied
    Re: Error Locking

    Have you tried copying just the memo field and a record id to a new table? Then you can remove the memo field from the main table and link to the new memo table in a set. Or you can pop up the linked memo record for editing - in which case it needn't be part of a set.

    Leave a comment:


  • Stan Mathews
    replied
    Re: Error Locking

    I wish there was a utility that printed all field rules into a list.
    Two exist. A5Doc and AIMS App Analyzer.

    Leave a comment:


  • draxx2755
    replied
    Re: Error Locking

    OK so what I did..... I duplicated my main table without records, indexes or anything else, into a new folder. Then I exported all the records to a csv file and imported them back into my new table. After that, I duplicated all other needed tables from the old db with records, indexes, etc.into the new db. I then copied all scripts from the old db into the new one. All seems to be working well now. The only thing I have left is to rewrite the field rules in the new main table. None of the old field rules were equation based. After looking at all of them in the old db, I saw they were all just simple lookups based on a list. So hopefully all will be working when my staff comes in Monday morning. I wish there was a utility that printed all field rules into a list. That would make things much easier. Thanks again for all the help guys, it is very much appreciated.

    Leave a comment:


  • draxx2755
    replied
    Re: Error Locking

    Hey guys I'm pretty sure that's the problem and I have dealt with it in the past I'm afraid. I ran the repair memo fields utility but it said all was well. As far as going back to a time when the FPT file was smaller, that would take me too far back and too much info would be lost. What I'm doing today is recreating the database. I've done it before, not much fun but it worked when I was done...lol. I just wish I knew what triggered this whole mess. Thanks for all the input though guys it is much appreciated.

    Leave a comment:


  • DaveM
    replied
    Re: Error Locking

    Stan got it first. I was looking it up LOL

    Leave a comment:


  • Stan Mathews
    replied
    Re: Error Locking

    There have been many threads dealing with corrupt memo files. You might try

    <TBL>.MEMO_CHECK()

    Leave a comment:


  • DaveM
    replied
    Re: Error Locking

    corrupted memo file has stopped most of us at one time or another.
    It is usually time consuming to figure out which record in the memo is the problem.

    Leave a comment:

Working...
X