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
Devcon 2020 Goes Virtual! LEARN MORE >

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

incremental fields

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    incremental fields

    Just updated from v1 to v4 of Alpha Five. In V1 I was able to set a field in field rules as an incremental field and stillbe able to change the contents of that field after it has been entered. According to the documentation with v4 I should stillbe able to do the same. However, if I change the field to something else, it changes back to the original contents as soon as I save the record or leave the field.

    Am I doing something wrong here?

    Thanks in advance.

    Gerry
    Tags: None
    #2
    RE: incremental fields

    Perhaps the terminology is getting in the way.

    I do not believe you can edit or change the value of an autoincrement field, as long as the field rule is in effect.

    You can manually remove the field rule, edit the record, and then restore the field rule if you need to. This is done by changing the field data entry rule from auto-increment to user entered, and then back again.

    -- tom

    Comment

      #3
      RE: incremental fields

      You can change an incremental field but you have to use a larger value. This prevents a value from being entered twice.

      Comment

        #4
        RE: incremental fields

        Allen, would you mind walking me through the steps? For me, if I have an auto-increment field and try to edit it's value using the default form or default browse, the new value flips back to the original as soon as the cursor leaves the field. Seems to make no difference if the 'new' value is larger or not.

        Thanks.

        -- tom

        Comment

          #5
          RE: incremental fields

          The value has to be changed when the record is created before it is saved.

          Comment

            #6
            RE: incremental fields

            Interesting. Never knew that! When I use the auto-increment field rule I also set the skip rule (in data entry) to .t., so I've never tried changing the value.

            Thanks for the info.

            -- tom

            Comment

              #7
              RE: incremental fields

              I use to be able to change the incremented field in V1. The field in question is the "stop number" field for route management. We are going to have approximatley 3,700 route stops to enter and want the self incrementing field at that time,but then we want the ability to change the number ona stop if it moves,etc.

              Now, in my own installation,it is no big problem to deactivate the field rule (in fact I had to do that). However, we are hoping tomarket this application and it won't be so easy to do that then.

              But thanks to all for you help

              Comment

                #8
                RE: incremental fields

                Gerry,
                If I'm understanding the problem try this:
                1) Make your field user entered rather than autoincrement
                2) create a table "nextroute.dbf" with one field nextroute#
                3) in the on save event of the form that allows you to enter the desired records, get the nextroute# from the "nextroute.dbf" table and do a set value with that value to the desired field.
                4) Increment the nextroute# and save it back to the "nextroute.dbf" table
                We do this a lot because it gives us more control of the actual generated number.

                Comment

                  #9
                  RE: incremental fields

                  Guys:

                  About auto increment...

                  I've had clients disturb auto increment in A4 - set new number sequences, etc. and it was a pain. I've been fooling around in A5 looking for ways [besides skip] to keep my users out of it. Here's what I found. With NO skip instructions in field rules. While editing the form, you can select properties for the field involved and set attributes to 'read only' there's a check box there.

                  Set in such a way, Alpha continues to Increment it, but the user can't get at it to change it. Ran into the problem while fooling around with an 'add on the fly' pick list which performed weirdly in 'Add' mode using a created form -other than default. We must realize, I guess that changing the field rules for a child in the set changes that child's field rules when used outside the set.

                  Just some thoughts....

                  Ken the Newbie

                  Comment

                    #10
                    RE: incremental fields

                    Oh Wow!! What a neat, although somewhat cumbersome, way to do it. Now, why didn't I think of that . I guess my big gripe is that in V1 I was able to do it the way originally outlined.

                    Thanks for the idea.

                    Gerry

                    Comment

                    Previous template Next
                    Working...
                    X