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

default value with auto increment

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

    default value with auto increment

    OK, I am having a brain *&%^ with this one.
    the field is chr - 6
    and format is 00-####
    i want the first 2 chr to = system year (right,2) that's ok
    then, i want the digits, after the "-" to autoincrement with each record, resetting to "0000" at a change in year.

    each year, on 1/1/"02", etc., I want the first two digits to change (that's ok)
    I use year(right(system->date,2)) and it works fine, but how to get the "0000" to reset on 1/1/02

    #2
    RE: default value with auto increment

    What about setting a conditional default value.
    value = YY-0000 if date = 01/01/YY and left(prev(key) = YY-1)

    This is obviously not code, more an idea.

    Comment


      #3
      RE: default value with auto increment

      Hello John,

      My guess is you will need to write a simple routine to deal with this issue along the lines of Thomas's reply. The auto increment rule will not do it unless you manually change it at the beginning of each year.


      Jim

      Comment


        #4
        RE: default value with auto increment

        Jim is correct. Forget the autoincrement.

        Check out Steve Workings field rule in the message thread entitled "autoincrement in set"

        A slight variation in Steve's rule should work for you if you have an index in the table on that field.

        Comment


          #5
          RE: default value with auto increment

          John, I posted an item in the code archive under SOLUTIONS that deals with incrementing. That script uses a separate table to store the increment value. When you create a new record, the old value is read, incremented one, and the new value replaces the old value in that table.

          Perhaps you could use the same general idea, and also store the date in that table. Then, when creating a new record, you could compare the date in the table with the current date and, if the year has changed, set the new value to 0000.

          Comment


            #6
            RE: default value with auto increment

            THANKS, BILL
            I WILL CHECK IT OUT

            Comment


              #7
              RE: default value with auto increment

              John:

              With the help of one of the A5 message boarders, I attached the following to the OnArrive event of the field that I wanted to increment...to get around the need to manualy intervene every year change...

              t=table.current()
              Dim newrn(1) as N
              Dim newrn2(1) as C
              Dim prevdate(1) as D
              Dim curdate(1) as D
              mode=parent.mode_get()
              if mode="Enter" then
              curdate(1)=t.dateofcall
              t2=table.open(t.name_get())
              t2.index_primary_put()
              t2.fetch_goto(t.recno()-1)
              prevrunnbr=t2.runnumber
              prevdate(1)=t2.dateofcall
              t2.close()

              if year(curdate(1))>year(prevdate(1)) then
              t.runnumber="0001"
              elseif t.patient="A" then
              newrn(1)=Val(prevrunnbr)+10001
              newrn2(1)=substr(str(newrn(1)),7,4)
              t.runnumber=newrn2(1)
              else
              t.runnumber=prevrunnbr
              end if
              end if

              It's a little diferent from your situation in that I don't store the year with the "incremented" number. But you could do that by setting the value = to the 2 digit year + the "incremented" number.

              Comment


                #8
                RE: default value with auto increment

                Ed,
                Thanks for the reply. I have copied your code and retained it in my development files. I have not tried it yet (just came back from fishing), but will try it tomorrow. thanks again.

                John Lemisch

                Comment


                  #9
                  RE: default value with auto increment

                  John- I tried to email you but didn't get through.
                  Just came across this old thread as I was hunting for a solution for the exact problem. Do you mind sharing how you finally resolved your problem?? THANKS!

                  Comment

                  Working...
                  X