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

AUTOnumbering Question

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

    AUTOnumbering Question

    I have a grid where ordernum is an auto increment field.
    The Grid is a data entry only. I notice the field has only <Auto> instead of actual number. This gets updated
    with proper number only after sumbit button is pressed. I tried using the inital value as Previous("worknum")+1 and
    that give me error.
    This scenario poses a problem. When I launch a second grid (line items) where ordernum is a field that is common
    to both grids (the child grid is dependent on the parent using ordernum field).
    Is there any way to know what the next number is going to be before hitting the submit button?
    I can use a test number as an inital value and that works. But not when I tried to use Previous function.

    #2
    Re: AUTOnumbering Question

    So you've got a main grid with OrderNum AutoIncrement field and then, from this grid, you open a line items grid. But you're not saving the main grid first? The only way the Auto number gets updated is when the data is physically saved. How about a "Save and then Open Line Items" all at the same time process.

    Comment


      #3
      Re: AUTOnumbering Question

      I would want to save the main grid only after saving the child grid because the user most likely wish to continue entering info on the main grid (consists of three different tab panes; and the child grid starting button is visible on the third pane).
      I was wondering how to determine the next autonumber programatically. I tried to use Previous function and that gave me error.
      When I use the browse function on this main table, I see the next number in the ordno field. But when I use web project control grid, I do not see it.
      My question is how to duplicate this functionality in the grid setup. Is there a property that can be changed to bring out the next available order number?

      Comment


        #4
        Re: AUTOnumbering Question

        This is a "chicken and the egg" scenario. You want to get to the child grid, but you don't have an OrderNum from the main grid and you don't want to get it yet. An age old problem but one that only has one flow of logic and, therefore, answer. Save the main grid, enter line items, get back to the main grid and continue entering.

        If you really want the next number you can get it, but it's fraught with danger. In Xbasic, get the maximum OrderNum entered. Then you'll know the next OrderNum... or will you??? 'Cause there's another user out there who already took that number while you're busying looking for it, and now you're in trouble.

        Comment


          #5
          Re: AUTOnumbering Question

          If it is really important to be able to enter all information before posting the main grid, you could opt for using a Dialog in v 11 with a repeating section. In this scenario, you can have the user fill in fields to their hearts content, and then, when they wish to submit, you can execute a sql query to post the primary record, get that auto-increment number, then post all of the child records.

          As I see it, this is the huge advantage of the Dialog component.

          I have an application where I have a master table with 4 child tables, and I can enter the information onto a single Dialog component, then submit to the master table, then submit each of the child tables one by one. Works like a champ. Plus, if the user decides to cancel the new record, you don't have to back out a transaction or anything like that.

          Of course, you can also wrap all of the activity into a start and end transaction in case something goes amiss in the middle.

          Best of both worlds. Chicken and egg...

          Comment


            #6
            Re: AUTOnumbering Question

            Oh, and David is absolutely right about the dangers of trying to get the next record number in a multi-user environment. Not a good plan at all.

            Comment


              #7
              Re: AUTOnumbering Question

              I am now convinced that I must abandon my original plan of getting to the next order number in some convluded way. Thanks to you all.
              Version 11 Dialogue is the answer (those repeating section is easy to use) for me. What an amazing development tool indeed.

              Comment

              Working...
              X