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

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

    Auto Increment

    I have an auto increment field with a format of N8.0
    When entering the record V6 is displaying the format with multiple decimal places. When exiting the field the data is correct but I had to open the field to make sure that I could verify the value. Doesn't the auto increment follow the format of the structure? Attached is a jpg.

    #2
    RE: Auto Increment

    Check the display / properties of the field object in your data entry form. Have you told Alpha Five to display decimals?

    -- t

    Comment


      #3
      RE: Auto Increment

      Yep I did check for that. N8.0 for both the structure and the object on the form.

      Comment


        #4
        RE: Auto Increment

        Maybe someone else can offer a suggestion. I never use numerics for auto-increment fields so I haven't ever encountered the problem.

        -- t

        Comment


          #5
          RE: Auto Increment

          I have auto incs in V4 & V5 with the same application and never saw this...

          Comment


            #6
            RE: Auto Increment

            Phillip

            I've seen this, but it works ok,

            What problem does it cause other than initial concern?
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment


              #7
              RE: Auto Increment

              In the field rules, on the data entry tab set the skip to .t. and you will no longer see this. This of course assumes that you do not want the users to be able to change data in this field anyway.

              I cannot tell you why this happens but my guess is that the way the autoincrement is working it is not setting the value when the record is entered but after the field has been tabbed through. I am basing this on the following that I read in the help files:

              The reason that the value that displays when the user starts entering a new record is called the "likely" value is that it is not really known until the record is saved what the value will be. For example, say a table has 4 records and two users begin entering a new record. User 1 will see the value of "5" in his new record. User 1 has not yet saved his record. User 2 now starts a new record. he also sees a value of "5". If user 2 saves before user 1 then his record will get the value of "5". If user 1 then saves, the "5" in the record will change to "6".
              Cheryl
              #1 Designs By Pagecrazy
              http://pagecrazy.com/

              Comment


                #8
                RE: Auto Increment

                Al, none whatsoever, other than trying to duplicate what I have seen in the past and my other employees do not freak out when they see a display different that what they have seen for years. I am going to try what Cheryl has suggested.

                Comment


                  #9
                  RE: Auto Increment

                  Cheryl, thank you, that did the trick...

                  Comment


                    #10
                    RE: Auto Increment

                    Phillip

                    I think Cheryl's idea works well.

                    I'm glad that it's not causing any additional problem, but there is nothing like call-avoidance for concerns and confidence level issues.
                    Al Buchholz
                    Bookwood Systems, LTD
                    Weekly QReportBuilder Webinars Thursday 1 pm CST

                    Occam's Razor - KISS
                    Normalize till it hurts - De-normalize till it works.
                    Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                    When we triage a problem it is much easier to read sample systems than to read a mind.
                    "Make it as simple as possible, but not simpler."
                    Albert Einstein

                    http://www.iadn.com/images/media/iadn_member.png

                    Comment


                      #11
                      RE: Auto Increment

                      Al, I couldn't agree more. I have spent the last 3 weeks redoing all the forms and this is the weekend to move everything to V6. As you can see I have been posting alot of threads. Some subtle some not...

                      I just want to feel confident that the move will be worth it. Come Monday I don't want a mutiny from the girls...they could care less about the upgrade...

                      Comment


                        #12
                        RE: Auto Increment

                        I don't know if this problem I have just run into with version 1550-2037. When I enter a record and on save a get an error that "numeric value cannot be entered into the field" (see attached jpg for corrent wording). The only numeric field is the auto increment field that for some reason does NOT follow field rule convention. I increased the field size in the structure to the max 19 and the error still ocurrs. Could this enormous number that is being generated by the auto increment causing the problem?

                        Comment


                          #13
                          RE: Auto Increment

                          I forgot the attachment

                          Comment


                            #14
                            RE: Auto Increment

                            Phillip:
                            I just stumpled on your thread, and I am a bit perplexed:
                            "" I have an auto increment field with a format of N8.0""
                            I have few questions:
                            1-Is this a character field with the seed value of N8.0?
                            2-Or is it a numeric field with 10 character/one decimal?
                            3-Are you allowing over-writing?
                            Somewhere down the thread, you wrote:
                            ""The only numeric field is the auto increment field""
                            Is that the same field at question at the begining of the thread?
                            Gabe

                            Comment


                              #15
                              RE: Auto Increment

                              let me save you some trouble:
                              It appears that:
                              1-In both posts, you are referring to the same field, and
                              2-That the field in question is a numeric one set to auto-increment with a start value of: 00000001.0
                              I'll get straight to the point:
                              What is the point of having a decimal in a numeric auto-incrementing field, or a character field for that matter??
                              I think that could also explain why alpha is behaving the way it is behaving.
                              Gabe

                              Comment

                              Working...
                              X