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

Incremant fields

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

    #16
    Re: Incremant fields

    Just an update of what John was really trying to achieve.

    After a brief chat, it turns out it was not a new report that was required but a number ON the report.

    This number is to be added to sequentially every time the report is printed.

    I recommended that a separate table with the report number be used as a lookup, this would be to get the current value and then to update that with xbasic if the report prints OK.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #17
      Re: Incremant fields

      A very big thankyou to you all for the help and guidance you have give me
      Especially Keith and Stan. You will be glad to know that my problem is sorted.

      Thanks again

      John

      Comment


        #18
        Re: Incremant fields

        John,

        Could you post how you resolved the problem.

        Thanks

        Alan

        Comment


          #19
          Re: Incremant fields

          Good Afternoon Alan

          The way I did it was to make an operation and perform a numeric calc by adding 1 to the field.
          This is run from a button on the form, First I preview the report then print it and then run the operation all with one click and the field now contains the report No for the next one.

          A good learning curve on Alpha and thank again for all your help

          Comment


            #20
            Re: Incremant fields

            Hi John,

            Please could you you give some more detail on this.
            The way I did it was to make an operation and perform a numeric calc by adding 1 to the field.
            Are you adding 1 to every record?

            If that is the case, then the first print run will have a value of 10 after the report has been run 9 times. This does not sound right.

            How are you getting the value of the last report number?
            Regards
            Keith Hubert
            Alpha Guild Member
            London.
            KHDB Management Systems
            Skype = keith.hubert


            For your day-to-day Needs, you Need an Alpha Database!

            Comment


              #21
              Re: Incremant fields

              certainly

              From a two-stat Button on the form :-

              1. I run a operation query to find all the records that have not been printed


              2. Run another operation update to add "1" to the fields for the report No. This is from:- operations, update then select numeric,perform a calc by selecting add 1 to the field. (if you have 50 records that have not been printed then those 50 would all have the same value)

              3. display and print the records


              4. Run another saved operation to update a field "printed" to true

              Having each record to have the report number in it is then an easy job to reproduce any report, that is why I went down this line.



              I know it might be a long way round but it works

              Thanks again keith for sending me on the right road to solve the problem.

              Regards

              John

              Comment

              Working...
              X