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

Corrupted database

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

    Corrupted database

    I have a corrupted database and not sure where to look. If someone can give me a hint?? Here are the symtoms:
    Expense table. Accounts Table. Expense amount posts to accounts based on account number. Expense "lookup" from account table for account number and account name. Account name from accounts table fills in expense "purpose" based on account number.

    NO, I can't restore to an earlier backup due to structure changes made since problem showed up.

    OK: Symptoms:
    1. Enter an expense. Enter account number and amount. The amount posts to accounts table in the account number one number higher than it should. If I enter an expense to accout 6100, it posts to 6150.
    2. I have subtract on delete rule. If I delete an expense for account 6100, the program posts to accounts and subtracts the amount from account 6150, one higher than it is supposed to.
    3. If I look at the expense table, the account number is correct but it posted to accounts in the next higher account number.
    4. After an expense has been entered. If I go to the expense table and try to change the account number, say from 6100 to 7100, I enter 7100 in the account number field and, as soon as I tab away from it, it changes to 7200, the next number up.
    The only way to make it stop is to delete the posting and lookup field rules. Rebuilding them brings the problem back again.

    I tried to make this as simple as I could but I know it ain't easy when reading someone else's descriptions.

    Jim
    Jim Belanger

    #2
    Re: Corrupted database

    IT ALMOST SOUNDS LIKE THE ACCOUNT NUMBER IS AN AUTOINCREMEMT FIELD. Could that be possible?

    Tom

    Comment


      #3
      Re: Corrupted database

      If not as Tom indicates, maybe an index problem--check to see if any have been truncated.
      Mike
      __________________________________________
      It is only when we forget all our learning that we begin to know.
      It's not what you look at that matters, it's what you see.
      Henry David Thoreau
      __________________________________________



      Comment


        #4
        Re: Corrupted database

        No, the account number is not an auto increment number.
        In the Accounts table It is a user entered number, always required, character field, simple mask 0000. In the Expense table it is character field, user entered, always required, validations "must exist in accounts table", lookup in accts table to fill in acct nr and purpose. It is set for "Force Closest match".

        Indexes:
        Expense table indexes all look OK except that A5 seems to have added an index. Index name _A5_Record_; Order Expression RECNO(), Ascending, include ALL.

        The Accounts table has the same index added. Plus, there are several indexes I don't ever recall adding. I'll check with prior backups to see if I can figure out when they were added. There are 5 more than I expected but they may be valid based on filters defined.
        Jim Belanger

        Comment


          #5
          Re: Corrupted database

          You said that in one table the account Number was Numeric, and in the other, it was a character. Are you converting one to the other when you test for "Must exist in"?

          Tom

          Comment


            #6
            Re: Corrupted database

            OOOPs, sorry. It is a 4 digit character field in both tables.
            I just deleted the extra indexes in the accounts table and it appear, right now without further testing, that the problem is gone. Gotta do more testing to determine that but I am in the process, right now, and will let you know.
            Jim Belanger

            Comment


              #7
              Re: Corrupted database

              Thank you to the suggestion to look at indexes. I deleted 7 indexes (all of them) in the accounts table. Alpha5 rebuilt two of them. The problem is gone. If I deleted an index I need, I'll cross that bridge when I get an error message!
              Jim Belanger

              Comment


                #8
                Re: Corrupted database

                Jim, maybe now is the time to re-think your backup strategy. <grin>

                -- tom

                Comment


                  #9
                  Re: Corrupted database

                  That's always a question aye? Well, I went back two months and the problem was there then, It just never popped up until someone entered the wrong account number for an expense and then tried to change it, then delete it. I checked another program that has been operating without problems for two years with the same engine and it has the problem too, too may manufactured indexes. So, I will need to modify that one too.

                  I have had index problems before. Usually, they are missing indexes that, for no reason, disappear. then, we get error messages. I haven't had a problem with extra indexes created by Alpha before though. This is a first for me.
                  Jim Belanger

                  Comment

                  Working...
                  X