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



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

Problem with APPEND UNIQUE

  • Filter
  • Time
  • Show
Clear All
new posts

    Problem with APPEND UNIQUE

    This one caught me by surprise. I am trying to APPEND UNIQUE records from File A to File B, based on a REFNO (Reference Number) field that is common to both files.

    When I executed the OPERATION, I received the following error: "Record number is past end of table".

    File A currently has 61 records. File B is currently empty.

    If I run a simple APPEND, I append 61 records - as expected. If ZAP File B and run the APPEND UNIQUE, based on the REFNO field common to both files, I receive the above error.

    There's got to be something VERY basic I'm missing.

    Any insight, as always, is greatly appreciated.


    Re: Problem with APPEND UNIQUE

    Think I found something. If I added a record to the File B, before I ran the APPEND UNIQUE, everything worked just fine.

    I'll continue testing but, any insight will still be appreciated.




      Re: Problem with APPEND UNIQUE

      I don't remember running into that before but it is logical. With no records in B Alpha looks at the first record in A, goes to B and tries to find if there is a matching refno, but there is nothing in B to match to so you get the error.
      There can be only one.


        Re: Problem with APPEND UNIQUE

        Thanks for the confirmation Stan.



          Re: Problem with APPEND UNIQUE

          Stan is correct with the reason for this. I rarely use Append Unique, preferring to run a routine to zap the dbf then add the records I need. Seems to work a bit better.


            Re: Problem with APPEND UNIQUE

            I do use append unique in certain instances. If the app was run on a laptop the lan and records were added to existing files. then it is a good spot for unique.

            My race car application can be run on a main computer, but the app can also be installed in a laptop for track use. Qualifying records are added to one or more cars and race records also get added. By doing a unique append, all those records are now on the main computer.

            Conversely, just copy all the records to the laptop before going to the race. This can be done from windows, no need to open the app for that one.

            Empty temporary table/set for a report = zap table and then append back the records needed for the report. No unique.
            Dave Mason
            [email protected]
            Skype is dave.mason46