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

Can't Append

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

    Can't Append

    I have always been able to append records with my script until today. Now it says 'unable to find file docume.dbf.
    I did NOT append it to or from that name. I appended from Sales to Invchgs.
    What is the problem here?
    Dwain

    #2
    RE: Can't Append

    Dwain,

    I did a search for "docume.dbf" in all topics in this forum, and found this thread:

    http://msgboard.alphasoftware.com/alphaphorum/read.php3?sortby=lastreply&direction=desc&num=11&id=58104&thread=58024

    There anothter user described hitting the same error when trying to append records which violated a field rule in his table. I suggest you review the thread, and then check your source records to determine if they contain field values that would be illegal under your current field rule regime in the receiving table.

    -- tom

    Comment


      #3
      RE: Can't Append

      I've done the above and more, but still won't work!
      I have a previous backup that I believe had everything working. I would only lose an hour or two of work. Would you recommend I restore it?
      Dwain

      Comment


        #4
        RE: Can't Append

        That's a judgment call for you, but it sounds reasonable to me. -- tom

        Comment


          #5
          RE: Can't Append

          After restoring, it still won't let me append! What Now?
          I duplicated the file and it behaved the same. No luck..
          Do you think Tech Service would be able to help? I really need a solution.
          Dwain

          Comment


            #6
            RE: Can't Append

            I suggest you create a model of your database and post it here with instructions on how to trigger the error. If the data is not sensitive a copy of the entire database will do, provided it can be compressed (zip) to less than 1MB.

            -- tom

            Comment


              #7
              RE: Can't Append

              To simulate the problem Click on Scripts; Play; Append to Sales. It also won't work by selecting Operation; Append.

              Comment


                #8
                RE: Can't Append

                Dwain,

                I'm confused.

                Your first post in this thread said you were trying to post from Sales to InvChgs.

                The only saved append operation is one which would append records from InvChgs2 to something called "Sales 2003".

                what am I missing?

                If you're expecting us to design a new append operation in hopes of seeing the error you're getting, we need step by step, mouse click by mouse click instructions from you. Please remember we don't know diddly about your data.

                -- tom

                Comment


                  #9
                  RE: Can't Append

                  There is also an often mentioned problem appending to tables with spaces in theie names. If you are truly trying to append to "Sales 2003", try renaming it to "Sales_2003" or some other name without a space.
                  There can be only one.

                  Comment


                    #10
                    RE: Can't Append

                    Click as follows:
                    "Quit" on my operating Menu
                    "View" on Invchgs2
                    "Scripts", "Play Scripts", "Append Records"
                    The append Genie appears with Master table Sales 2003.
                    Select C:\Invchgs2.dbf, "Next"
                    "Yes fields have same Names, "Next"
                    "Yes (Checks for Duplicates), "Next"
                    In Master Table check for Duplicates, 1st one "An"
                    2nd one "Invnb", "Next", All Records, "Next", "No"
                    "Next", Run but do not save definition or Run and save, it makes no difference. Finally OK. The summary screen appears.

                    Dwain

                    Comment


                      #11
                      RE: Can't Append

                      Dwain,

                      The validation rule you have in the Sales 2003 table doesn't make sense. I deleted it. I then was able to append 9 new records from InvChrg2 from the 397 candidate records. Presumably the others duplicate the AN and INVNB fields of records already in the Sales 2003 table.

                      I'm using the Home Edition of A5V6 build 1506.1058

                      -- tom

                      Comment


                        #12
                        RE: Can't Append

                        Let me try to attach the return copy of the database again.

                        -- tom

                        Comment


                          #13
                          RE: Can't Append

                          That validation rule has been doing a great job for many months even if it doesn't make sense. It was catching duplicates from both tables. Did you just leave it deleted or did you improve on that rule.
                          Presumably I can just correct mine and won't have to download yours. Is that correct?

                          Dwain

                          Comment


                            #14
                            RE: Can't Append

                            Dwain,

                            I am not familiar with your data, so you will have to be the judge. I suggest you experiment and test carefully with both approaches. The append operation itself is configured to skip the append if the transaction record duplicates field values in any record in the master table.

                            My experience here is that when the field validation rules were in effect in the master table zero records were appended, and 9 of the 397 records were kicked over to the VIOLATED table, since they failed to meet the validation rule requirements. I have yet to see the error message you reported at the top.

                            -- tom

                            Comment


                              #15
                              RE: Can't Append

                              Dwain,

                              here's an image of the validation field rule that troubled me.

                              Sales 2003 is the master table in your append.
                              InvNb field in this table is the one with the validation rule, and is the one show in the attached image.

                              As I read this rule records are PERMITTED to be entered in the master table only if the "new" InvNB field value is not already found in the master table AND the "new" InvNb field value is not already found in the InvChrg2 table.

                              The problem is this. The InvChrg2 table is your transaction table in the append. Every record that Alpha Five tries to append to the master table will of course have an InvNb field value that is already present in the transaction table.

                              Am I missing something?

                              -- tom

                              Comment

                              Working...
                              X