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 PO Number

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

    Auto PO Number

    I am using the following formula to create a Purchase order number.
    right(str(year(date()),4,0),2)+padl(str(month(date()),2,0),2,"0") + padl(str(day(date()),2,0),2,"0")
    Problem is- all my PO#'s for the day are the same.
    Is there a way to add a -1, -2 etc. at the end?
    Something like this. If the date for today has already been used add a - 1 to the end. Then the next won would have a -2 added etc.
    Thanks.

    #2
    RE: Auto PO Number

    would it be possible to perform a dbsum or total calculation to determine how many existing PO's there are for a given day, and then add "1" to that number?
    Thank you,
    Mike Konoff

    Comment


      #3
      RE: Auto PO Number

      Hi,

      I do something like this by using a separate autoincrement field and using that in the calculation as well. For example, if you never have more than 99 purchase orders in a day, you can multiply your original calculated PO# by 100 and add the autoincremented field to it. There would be no hyphen, but your last 2 digits would be different for each purchase order that day. Also, you would need to restart your autoincrement with the number 1 each day.

      Best regards,
      Robin

      Comment


        #4
        RE: Auto PO Number

        Jeff

        One other suggestion is to set the default value in field rules to DBMAX()+1 or PREVIOUS()+1.

        If you use PREVIOUS(), make sure you set the index for it.

        Hope this will help.

        Comment


          #5
          RE: Auto PO Number

          Jeff
          I would do something like this
          Create a table i.e. �pono_num� with a field called �pono�

          And use this code to get your PO #

          ids = table.open("pono_num")
          ix = ids.index_primary_put()
          if ix.records_get() = 0
          ids.enter_begin()
          ids.pono = right(str(year(date()),4,0),2)+padl(str(month(date()),2,0),2,"0") + padl(str(day(date()),2,0),2,"0")+"-1"
          ids.enter_end(.t.)
          LR = ids.pono
          elseif ix.records_get() >0
          ids.fetch_last()
          LR = ids.pono
          if left(LR,6)!= right(str(year(date()),4,0),2)+padl(str(month(date()),2,0),2,"0") + padl(str(day(date()),2,0),2,"0")
          ids.change_begin()
          ids.pono = right(str(year(date()),4,0),2)+padl(str(month(date()),2,0),2,"0") + padl(str(day(date()),2,0),2,"0")+"-1"
          ids.change_end(.t.)
          else
          ids.change_begin()
          ids.pono = left(LR,7)+ltrim(str(val(right(LR,len(LR)-7))+1))
          ids.change_end(.t.)
          end if
          end if
          NR = ids.pono
          ids.close()
          new_pono = NR

          Daniel Weiss
          Daniel Weiss
          EZ Link Software

          Comment


            #6
            RE: Auto PO Number

            As the many examples demonstrate, there are a couple ways to do this. Attached is an example using a variation of Mike's idea. I use something similar in a couple databases and prefer using the CanSaveRecord event in field rules. In this way, the new number is not defined until it is saved. This reduces problems in a networked situation.

            The code is fairly simple. It requires an index on the po number field and uses tablemax() to get the last po number.
            Is then checks the left side of the po number that is derived form the date and checks if is todays date. If it is, it checkd the value of the unique right part and increments it 1. If the last entered is not today, it starts at todays first value.

            Unzip the table and attach it to any database. Open the field rules and check the event code. If you open the default browse, enter any value in the text field. When the record saves, the new po number is created.

            Jerry

            Comment


              #7
              RE: Auto PO Number

              Here is an example I worked up for another A5 user. This may help.

              Dan
              Dan

              Dan Blank builds Databases
              Skype: danblank

              Comment

              Working...
              X