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

duplicate records solved but why??

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

    duplicate records solved but why??

    duplicate records solved but why??

    the button from main menu opens the order form in new record mode

    the new record form has various search buttons on it

    the find button generates a duplicate header

    topparent.index_set("ORD_NO")
    topparent.find()

    when this button is pushed the form shows the last order entered
    (form is opened in record number oreder)

    you can eneter the order no you are looking for in the find prompt
    box and will show it, thats ok

    so the creation of the duplicate header is created on pushing the find
    button which was created by the genie

    however if the previous record button is pushed and then the find no
    duplicate record is created
    parent.fetch_prev()
    END

    the work around is to place a cancel command in the find button
    parent.cancel()

    but why does the previous button not create a duplicate and
    the find does?

    is this the right procedure or a better method to open a form for
    new records but allow the user perform various searchs while in the new record
    form???

    perhaps i have some made some bad assumptions(as usual) but would
    very much like to hear if this is a common approach

    thanks all

    #2
    RE: duplicate records solved but why??

    John,
    I make it a rule not to permit my users to navigate within a table while data entry is still pending. Otherwise, they wind up saving partially completed records as soon as the record pointer moves. Often without realizing it. Once data entry starts I disable all navigation, and force the user to save or cancel the pending change before they regain the ability to move to a different record. It's probably possible to design a system that's more flexible, but for me, at least in this instance, I prefer to keep it simple.
    -- tom

    Comment


      #3
      RE: duplicate records solved but why??

      John,

      Out of curiosity I tried to duplicate what you describe using the default browse for one of the tables in the invoices sample which ships with Alpha Five.
      I found that once data entry started in a new record, if I hit the previous record vcr icon, data entry ended and the record pointer moved to the correct record.
      I found that once data entry started in a new record, if I select find by key from the menu, data entry ended and the record pointer moved to the correct record.
      In neither instance was an unwanted record added to the table.

      I suspect that another script associated with your data entry form is saving the new record, perhaps when you aren't expecting it.

      --- tom

      Comment


        #4
        RE: duplicate records solved but why??

        tom thanks for your input

        i to spent alitle time in trying to create the same situation
        in the sample but

        it takes a lot of work/time to create the same situation from the sample
        which unfortunately i can't take at this time,

        i'm in solving the problem in a live situation with no back up system

        but i'm pretty confident i can create it,
        what made it more dissappioting is that the first field was set up
        as unique (no duplicate allowed) yet it does,
        well if i can create a situation that creates duplicates unique order
        no, well , well i just didn't figure that i could violate a field
        rule like that, and spend time preventing it,(i thought that was
        field rules job.

        anyhow thanks again for your response and hopefully inthe near future
        i can address this in much more detail and resolve what i did to do
        this--in the meantime i hope the fix i put in holds up and does not
        create another situation

        thank you

        Comment

        Working...
        X