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

Updating an auto increment field

  • Filter
  • Time
  • Show
Clear All
new posts

  • Updating an auto increment field

    I need to update certain records in an auto increment field based upon certain criteria, however after defining the update I get the message that I cannot update an auto incremented field. ??? Had no problem with this in V1.02. Is there a workaround for this. It is essential that I be able to do this and then sort on the updated records. Any help would be appreciated.
    Don Hutchinson

  • #2
    RE: Updating an auto increment field

    You will need to go the field rules and change the field to a "user entered" field to run the update then change it back afterward.

    Just remember that in A5v4 the autoincrement is based on the last record in the table using record number order. This even includes any deleted records at the end of the table. (They're still there but they aren't visible.) So, if your update causes the highest value to be somewhere other than the end of the table, you may end up creating duplicate values at some point in the future.


    • #3
      RE: Updating an auto increment field


      Thank you for your response. Problem is I cannot go this route. I cannot have my operators going in and mucking about in the field rules and besides it is to slow.

      I have come up with another workaround where I duplicate the table (just records and index's) to a dummy table (in this case register2) where the autoincrement field has been changed to user_entered, run the update and then duplicate the table back to the original table (register).

      The script is:

      saved = table.current().filename_get()
      dbh = db_reset("c:\program files\a5v4\files\register.dbf", FILE_RW_SHARED)
      dest = ("c:\program files\a5v4\files\register2.dbf", "N")
      if dest != ""
      db_duplicate(dbh, dest, 5)
      end if
      dbh = db_reset(saved, FILE_RW_SHARED)
      Update.Run("reg2 [email protected]:\program files\a5v4\files\register2.dbf")
      saved = table.current().filename_get()
      dbh = db_reset("c:\program files\a5v4\files\register2.dbf", FILE_RW_SHARED)
      dest = ("c:\program files\a5v4\files\register.dbf", "N")
      if dest != ""
      db_duplicate(dbh, dest, 5)
      end if
      dbh = db_reset(saved, FILE_RW_SHARED)

      This works well behind the scene and is pretty quick.

      However, when I try to run this script from a button on a form I get the error message.

      "Unable to reset current table from within a card.A table reset may be done from a scrip that is run using the new script_spawn command"

      I can find no documentation concerning this command. How and where does it work???



      • #4
        RE: Updating an auto increment field


        For many of us autoincremented fields are used as link fields which hold our sets together. We actively discourage the endusers from editing any link field values, and would really, really, have to be pushed into a corner in order to be persuaded that it was necessary to run saved update operations against them. Frankly, I think it's likely to be a dangerous practice.

        If your autoincrement field is not being used to link your tables together into sets, you might consider abandoning it in favor of a default value field rule, tied to a 'last used' figure you save on disk somewhere. You could suppress edits by making your field 'read only' on all data entry forms. You could then run your update against the field without worrying about the autoincrmeent field rule at all. The tradeoff would be adding a bit of code to update the 'last used' figure on disk after each new record is saved.

        -- tom