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

Auto Increment Behaviour

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

  • Auto Increment Behaviour

    Hi,

    I have reported this as a bug but not sure if this is deliberate. Could others please check this out?

    In V4.5 the auto increment behaviour moved the value up one for each new record and if any recent records were deleted the value skipped their unique numbers (leaving a gap) so the same unique value would never be re-used unless the table was packed. This is how I prefer.

    In V8 and V9 enter a few new records then delete them and the value starts again prior to the value before deletion even though no pack had been run.

    For example the user could enter a few records today and say post or update data etc in other linked tables based on the unique value but then open the table say tomorrow and if any recent records had been deleted and new records added the user would be passing values from different records to other linked tables but using the same unique number of a different record created yesterday.

    I know we can write our own incrementing numbers and delete records from within a set but I have pre-built built apps based on the behaviour of V4.5 and previous. I much prefer the old behaviour.

    Michael
    www.instantnurserymanager.co.uk

  • #2
    Re: Auto Increment Behaviour

    Michal, the behavior of the autoincrement field rule changed in 2002 when vers 5 of Alpha Five was released. There have been no changes to this since so far as I know. Instead of using the last physical record in the table to get the "seed" to be incremented, the field rule uses the "highest" field value, determined by index sorting.

    The problem you fear stems from the failure to delete linked child table records when the parent table record is deleted. In the scenario you describe children are "orphaned" when their parent is deleted. Orphan records should be deleted first, before deleting the parent.

    Given the length of time that's passed I think it's unlikely that "old behavior" will be restored. Would break too many apps that have been built with A5v5, A5v6, A5v7, A5v8 and A5v9.

    Comment


    • #3
      Re: Auto Increment Behaviour

      Tom,

      Thanks, according to your comments, this is obviously not a bug but intentional for some reason.

      I much prefer the old behaviour since it guaranteed a unique value. I often pass values from one table to another based on a key value of tables from outside of a set.

      Michael

      Comment


      • #4
        Re: Auto Increment Behaviour

        Michael, I see what you mean. One of the advantages to the change is that you get the same "next" number whether the table has been packed or not. This was not true with vers 4.5 and earlier iterations. In your app you are able to keep things straight only by assuring that the table is never packed. I suspect that many more users pack than never pack. -- tom

        Comment

        Working...
        X