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 numbering

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

    auto numbering

    Hello...I am very much a newbie when it comes to writing scripts. I have created several databases using the wizards. I want to create a file management database that will track where files are stored (in file cabinets). I have a location code, numeric 3 in length (ex, 10, 20, 30) a sub category code, numeric 3 in length (ex, 10, 20, 30) and a file number (auto increment).
    I want the file number to be the location code + the sub category code + the file number. Is there an easy way to accomplish this?? Ex: for location code 10, category code 20, file number1 :the file number would be 01002000001, 01002000002, etc

    Thanks...Rose

    #2
    RE: auto numbering

    Rose,

    I'm a "know nothing at all" when it comes to xbasic. I'm sure you'll get many great way's to handle this. There's quite a few talented people that frequent this board.

    But, I think that I may have a solution for you, and I'm really glad to be able to offer my help. (Returnt the favor)

    I'd include another field in the database. Let's say you call it COMB_CODE, for combination code, or call it what you like.

    I'd set the 3 fields you already have, and the new one, to be character fields. I'd then set the Field Rule for the 4th field COMB_CODE to be calculated with the following calc statement.

    ltrim(location)+ltrim(subcat)+ltrim(filenum)

    If location=50, subcat=60, and filenum=00001, then comb_code would = 506000001.

    Give it a shot.

    Mike
    Thank you,
    Mike Konoff

    Comment


      #3
      RE: auto numbering

      Hi Rose:
      I would create another field numeric 10 in length and then concatenate the first three fields into that field. You can do that using field rules, so you won't have to use any scripting.

      Hope that helps.

      Dan
      Dan

      Dan Blank builds Databases
      Skype: danblank

      Comment


        #4
        RE: auto numbering

        Hi Rose
        The filenumber field will have to be a character field if you you want the value to be able to start with a zero. Heres one way to do it:

        PADL(LTRIM(STR(LOCCODE)),3,"0")+PADL(LTRIM(STR(SUBCODE)),3,"0")+PADL(LTRIM(STR(FILE)),5,"0")

        You have to turn the numerics to characters, set how long you want the string to be, and then set how you want it padded. PadL means put whatever to the left of my value, and put as many of whatever to make it the length I want. So in the first part, its padding with "0", and adding as many zeros as needed to make the value 3 characters. If the loc_code was 100, there would be no leading zero. If its 2, then it returns 002. and so forth...

        Mick

        Comment


          #5
          RE: auto numbering

          Thanks a million Mike ....I will give it a try!

          Comment


            #6
            RE: auto numbering

            Rose,

            First, I would recommend changing the "Numeric,3,0" fields to "Character 3". This will allow you to have values like "020". Otherwise, if you enter "020" you will get "20" and it will be difficult to get the output you want. The general rule is, "If you aren't going to do math with it, use a character field." The character field can have a mask which allows only numbers. (Use # as the mask character.)

            Same for the auto-incremented file number - make it a character field. The first value might be "000001" or any other starting number you want but be sure there is a character in every position; ie, use leading zeros if necessary until all positions are filled. (You don't strictly have to do this but, if not, you will have a much harder time getting a consistent output string.

            Finally, decide where you need to have the completed File Number and how it will be used. If you only need to display it on forms and/or reports (this is often the case) then you don't need to store it as a separate field. You can simply define a calculated 'field' object on each form/report which is:
            location_code + sub_category + file_number

            Also, if you want to sort by the total number, you could simply define the index/query to be the sum of the 3 fields. Sorting of the component numbers will work just like a numeric sort IF you include the preceding zeros (see below for more about this).

            If you really feel the need to store the actual value in the table, just define a calculated field using the same expression as above. (You may have noticed that I don't think this should be necessary - it's just a waste of 'not very valuable any more' hard drive space in my mind.)

            Here's another reason to define the fields as characters! If you used numeric values, you would need an equation like this:
            right("00"+ltrim(str(location_code)),3)
            or
            padl( ltrim(str(location_code)), 3, "0" )
            just to convert the location_code field - then do the same to all the rest and add them together!

            Preceding zeros: If you are concerned about the user forgetting to enter preceding zeros, you can solve this with a simple "CanWriteField" event in the field rules:

            DIM GLOBAL a_field_value as c
            a_field_value = padl( trim(a_field_value), 3, "0" )

            This will convert "1 " (a "1" typed in the first position only) to "001", etc.

            Comment


              #7
              RE: auto numbering

              Wow! There were no answers when I started my response and there were already 4 others when I got done!

              Comment


                #8
                RE: auto numbering

                lol... our little fingers are still smoking! (humming the theme from Bonanza)

                Comment


                  #9
                  RE: auto numbering

                  Thanks to all......my heros!!!

                  Comment

                  Working...
                  X