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

Input with a form differently

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

    #16
    Re: Input with a form differently

    Originally posted by totalbiz View Post
    Hi Robin,

    What is happening is that I have a customer that I wrote a shipping application for and it generates with an auto-increment a sequence number. The customer wants to see this sequence number without any breaks in sequence without an explanation. The problem is the users go into the application all day long and they might make a mistake and want to cancel what they are doing. This happens a lot so there are a lot of records which are "blanks", or records with a sequence number but aren't a valid shipping record. I thought if I could add the record after the form shows and entry is done that it would avoid this problem.
    Hi Don,
    It sounds as though the form they are viewing allows continuous enters which creates the incomplete record. If the form opens in recno order to the last record that might help if all they want to know is the last number used. You might also prevent the saving of a form unless key fields have been completed and require the use of your button(s) to save, cancel or delete it.

    How and why users do what they do is a mystery even when you stand there and watch them!
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


      #17
      Re: Input with a form differently

      why not have a table called controlData and keep next invoiceId, next checkId, next smethingId and when ready to save the record the xbasic will go get that number and update that number +1 and create a new record with the retrieved number? so if the record is cancelled no new record is added. I would imagine that this will require an xdialog from than table tied regular form.

      edit: I see this is suggested in post #15
      thanks for reading

      gandhi

      version 11 3381 - 4096
      mysql backend
      http://www.alphawebprogramming.blogspot.com
      [email protected]
      Skype:[email protected]
      1 914 924 5171

      Comment


        #18
        Re: Input with a form differently

        Originally posted by Tom Cone Jr View Post
        Don,

        Is the data entry form based on a single table or a set of tables?

        -- tom
        Hi Tom,

        It is a set but I will only allow entry of the fields in the child table when the parent record has been added.

        Comment


          #19
          Re: Input with a form differently

          Originally posted by Charles Hoens View Post
          Don,

          If I understand you, this is what I am currently doing for a client.

          I created a config.dbf in which ...

          Not sure if this is where you are going, but I hope it might help.
          Hi Charles,

          Thank you for the reply. This seems to be the approach I need to take.

          Comment


            #20
            Re: Input with a form differently

            Don,

            It sure sounds like you need to change your data entry sequence. I'd investigate the use of a new tables and a new set. The new tables would have the same structure as your current tables, as would the new set. Do your data entry using forms based on the new set. Data entry would essentially be on a scratchpad. Provide a button they would use to commit the new records to disk, and then create new records in your "real" tables, assigning field values from the scratchpad records.

            Use the scratchpad only for entering new transactions.

            Comment

            Working...
            X