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

Appending Records To A5 From A4

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

  • Appending Records To A5 From A4

    Recently, appended records from A4 to A5 came over incorrectly.

    Records in two separate dbf files in A4 --header.dbf and items. dbf
    needed to be appended into (2) A5 tables Invoice_header and items_invoiced.

    The items_invoiced appended correctly. The invoice numbers appended were from R744 to U966.
    However, the appended records into invoice_header showed invoice numbers from R744 to V496.


    The values in V496 were identical to (the last value) U966. The appended values in U966 made no sense at all.

    This morning, I removed the incremental field rule for invoice number in the
    A5 table "invoice_header" , emptied the table and re-appended from A4.

    This time the data came over correctly.

    It seems as though the incremental field rule works overtime as records are being appended.
    If any one else has had a similar problem, I would like to know how they resolved it.

    John Linley

  • #2
    Re: Appending Records To A5 From A4

    John, I see that no one has written in reply. If memory serves what you experienced is how Alpha Five was designed to work, and your solution is the way to assure that the invoice numbers aren't changed by the field rule. The auto-increment field rule is an "engine level" rule that will be enforced whether the new records are created through a form or not.

    -- tom

    Comment


    • #3
      Re: Appending Records To A5 From A4

      to: Tom Cone, Jr

      I posted the append message hoping it might help others, and to see if anyone else had a different solution. I was also wondering if I was neglecting some unnoticed feature in the append genie. Thanks for noticing,
      and the response.
      Regards, John

      Comment


      • #4
        Re: Appending Records To A5 From A4

        Originally posted by john linley View Post
        to: Tom Cone, Jr

        I posted the append message hoping it might help others, and to see if anyone else had a different solution. I was also wondering if I was neglecting some unnoticed feature in the append genie. Thanks for noticing,
        and the response.
        Regards, John
        An additional post from A4 to A5 problem..

        In transferring records (5833) from A4 to A5, I encountered an error message, suggesting a numerical field was too short.

        I checked the A$ table and the A4 table and both were of the same length. After considerable failures, I finally duplicated the A5 table, but without the field rules. The append operation worked perfectly with the duplicate table.
        I will research each field rule to further define the problem. Having pre-defined incremental field rules
        or some other unusual post or calculated field rule seems to abort or interfere with appending data. Will add to this when I find the culprit.
        John Linley
        Last edited by john linley; 07-29-2010, 12:18 PM. Reason: culprit located!!! - mea culpa - fiimpreld rule for week " week(inv_date) "

        Comment

        Working...
        X