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 field rule

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

    #16
    Re: Auto increment field rule

    OK, here is what I am getting:
    1-If you start with 3 C field and reach 999 then increase to 9 C field, the next increment will be "999000000"

    2-If you start with 9 C field and your initial value is
    Code:
    "      001"
    after you get to:
    Code:
    "      999"
    crazy stuff will happen.. Alpha will start using alphbet, but will put the "a" in the next field not the autoinc field! confirming my suspicion that you reached your limit but as alpha is still incrementing, it adds to the next field in the table!

    3-If you start with 9 C and your first value is:
    Code:
    "        1"
    right after 9 alpha will roll to 000000009
    Not quite as messy as the second scenario, but still messy.

    So, to answer your question, what would I do to fix it?

    I would select all values less than 999000000 trim them then pad them with zeros from the left.
    Hopefully you haven't added a lot of records starting with the 999000000 because if you have, you left a gap the size of the Grand Canyon between 000000999 and 999000000.
    If you haven't added alot, change them manually. If you have, then we are off to some expressions to change 9990000000 to 000001000 and to change 999000001 to 000001001 and so on.
    It shouldn't be a complicated expression, but whatever you do with the parent you do with the childrern.

    That's one good reason why I either do my own autoinc or use numeric.
    Last edited by G Gabriel; 07-08-2007, 03:08 PM.

    Comment


      #17
      Re: Auto increment field rule

      In my situation I had a 10 character field, with the the numbers starting at 1 going through to 4967 . I also had a conditionally required rule set as only required for orders made after 01/01/2002 as older orders didn't have a reference number.

      The end user stopped entering data when we upgraded to v8 and saw that the numbers went out of sync so I have deleted that record, reset the field rule to numeric and now when reenetering the deleted record it allocates the expected ref no.

      At the average rate of 1000 orders per year I don't see running out of numbers as an issue here.

      I can now concentrate on the other things that haven't translated from v4.5 to v8 so well. (such as on-push commands for printing invoices)

      Comment

      Working...
      X