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

    Auto Increment Field Rule

    Is there an X-Basic command to turn the auto-increment field rule for a field on and off ?

    Thanks

    Andy Sigrist

    #2
    RE: Auto Increment Field Rule

    I don't think so. -- tom

    Comment


      #3
      RE: Auto Increment Field Rule

      Why would you want to do this?

      Charles
      SwissCharles
      Between the Alps and a comfy place

      Comment


        #4
        RE: Auto Increment Field Rule

        I am planning to archive old Work Orders to a secondary DBF file.

        Another routine would allow the user to recombine (re-append) the archived records back into the Work Order file.

        If the autoincrement is left on, the archived Work Orders will be given new Workorder numbers during the append session.

        If I can turn off the autoincrement during the append operation, I can recombine them while preserving the original Work Order numbers

        Andy

        Comment


          #5
          RE: Auto Increment Field Rule

          Hi Andy,

          This may be the long way around accomplishing what you need, but if you do not get any other options from other people here, you could give it a try.

          Copy the entire table to a new table, then delete records from your copy based on a range of workorder numbers. I believe this will give you the end result you are looking for.

          Cheryl
          Cheryl
          #1 Designs By Pagecrazy
          http://pagecrazy.com/

          Comment


            #6
            RE: Auto Increment Field Rule

            Andy,

            This may touch on more philosophical aspects than technical ones.

            For a start, I would refrain from shuffling records back and forth just to indicate their changed status (from 'active' to 'archived').

            If I get you right, you want to 'archive'certain work orders but be able to 'un-archive' some of them at a later time while preserving their original work order numbers.

            In similar circumstances I would just add a field to the work orders table called 'WO_Status' containing choices like 'active' 'inactive' 'investigate' and some such, you get the idea.

            Then, by just setting a view-filter on the value of the 'staus' field according to the records you want to see (being in the form of a script in a button or a predefined filter in a forms property, etc), you get all the records you do not want to see easily out of your way. Un-archiving a record then becomes the simple matter of changing the value in the 'status' field.

            This solution is also more in line with relational theory...

            HTH

            Charles

            SwissCharles
            Between the Alps and a comfy place

            Comment


              #7
              RE: Auto Increment Field Rule

              Andy, I have that scenario in a couple of situations, as the table otherwise becomes too large.

              My approach is to use a roll-your-own autoincrement, and it then never beecomes an issue.
              Cole Custom Programming - Terrell, Texas
              972 524 8714
              [email protected]

              ____________________
              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

              Comment


                #8
                RE: Auto Increment Field Rule

                So far I used to "archive" records just based on their status like suggested in an earlier message. But like you mention, in time the files just get too large.

                For this reason, I decided that I do want to split them off physically into a different DBF now.

                I may have to go to my own auto-increment routine as well. On the other hand, I thought there should be an X-Basic command to turn the auto-increment on and off. After all there are commands to set all kind of other field properties on forms through X-basic.

                Thanks for your help

                Andy

                Comment


                  #9
                  RE: Auto Increment Field Rule

                  Andy,

                  I don't think there are any field rules that can be enabled or disabled using xbasic scripts. My guess is that this is by design. They are intended to work regardless of which form or browse layout is being used to edit records in the table. Unlike field object properties in your form they are not tied to a particular form.

                  -- tom

                  Comment


                    #10
                    RE: Auto Increment Field Rule

                    Andy,

                    When you write: "But like you mention, in time the files just get too large."

                    These are genuine questions:
                    How does this manifest itself?
                    How large is 'too large'?
                    Are you talking about fetch-times?
                    How many records do you have in said table and how many fields per record?
                    How are the indexes set up?

                    Charles
                    SwissCharles
                    Between the Alps and a comfy place

                    Comment

                    Working...
                    X