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

Append problems

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

    Append problems

    OK Guys...

    This should be a breeze for most of you, but my head is getting bloody from repeated contact with the wall.

    I am having trouble appending records from an old database application to a revised version.

    The databases were not changed, same field names, number of fields etc. After building new reports, screen changes, etc., I emptied the new working database and prepared to append the records from the original database into the new one.

    I used the operation genie to create the append. The master database table is "spokes.dbf" and the transaction database table is "spokes2.dbf." When running the append, the program gives an error message of @Spokes2->amountpd2 not found. However, opening the operation in design mode both field are clearly listed with identical spelling and mapped to each other. Both are numeric fields, length 8 decimals 2. I then mapped another field from the transaction database to the apountpd3 field in the master. Same error.

    I then tried to delete the amountpd3 from the append operation entirely. I saved the append, ran the operation and got the same error. I deleted the append created by the genie and manually rebuilt. Same error.

    There are aboud 35 fields in each database ... the amountpd3 field is about 20 in the list.

    It must be something simple that I am overlooking. Any suggestions would be appreciated.

    Rich
    Richard

    #2
    RE: Append problems

    Sometimes Alpha's error message is close, but not quite correct.

    You might poke through your transaction data and see if any of it is outta whack. Or perhaps a field rule is begin violated.

    - Steve
    -Steve
    sigpic

    Comment


      #3
      RE: Append problems

      Steve ...

      I looked at the data in the transaction file and it all seemed OK. There were no field rules on the amountpd3 fields in either database.

      Any other toughts?????
      Richard

      Comment


        #4
        RE: Append problems

        Richard:
        Try 1 or 2 fields at a time
        if it works then add another field until you fine the field that is causing the error.
        might take a while but it should work.
        Charlie Crimmel

        Comment


          #5
          RE: Append problems

          Richard, the type of problem you describe is most often related to the values stored in the transaction table. Data within that table is corrupt, or possibly you have a mismatch in the table structures. If I were having this trouble I would double check to verify that the data types and lengths are identical. Then, if that proves true, I would divide the transaction table into smaller chunks and append one at a time until I found the chunk that would not append. Then I'd subdivide that chunk further, until I got to the troublespot. Tedious to be sure, but likely to succeed... eventually.

          -- tom

          Comment


            #6
            RE: Append problems

            Richard,

            You say, "The databases were not changed, same field names, number of fields etc". Why not just copy the *.dbf files from you original database to the new database. Include .FPT if you have memo fields.

            Tom

            Comment


              #7
              RE: Append problems

              In the new database/application. I did cre4ate some new global calculated fields for reports, etc.

              I was not sure where they were stored and if they would be affected ifr I simply copied the table. The application does have a memo field.

              I give some of these suggestions a spin in the morning. I figured 6.5 days in the office was enough.

              Thanks for the input ... I'll keep you posted.

              Thaks again.

              Rich
              Richard

              Comment


                #8
                RE: Append problems

                I happen to be in the process of moving the databases that I developed in Alpha Four over to Alpha Five. Whenever I make the move I simply copy the table from the old directory from A4 to the new directory in A5, and then begin re-building my field rules, forms, reports, etc.

                As suggested in a previous post, if your original table is *.dbf format, you should not have any trouble copying that to your A5 directory and start working from there.

                Mike
                Thank you,
                Mike Konoff

                Comment


                  #9
                  RE: Append problems

                  Thanks for the reply. I duplicated the original A5 database, including field rules, etc.

                  Then ran the append operation. Things worked just fine. Not sure what the problem was ... but finally got the job done.

                  thanks to everyone for their suggestions and help.

                  Rich Hill
                  Richard

                  Comment


                    #10
                    RE: Append problems

                    [code]
                    Try this.

                    Copy your new table to a temporary file.
                    then use the copy function below to copy old table to the new one.

                    Then manually copy your required ddd,ddm,ddx files back to get the layouts as required.

                    Hope this is of use to you.

                    Ron




                    '-----------------------------------------------
                    function copy_table as L(copy_from as C,copy_to as C, copy_data as L,copy_rules as L)
                    '-----------------------------------------------
                    on error goto error_handler
                    dim quit_option as C

                    '-----------------------------------
                    ' validate file extensions
                    '-----------------------------------
                    if at(".dbf",copy_to)

                    Comment

                    Working...
                    X