Results 1 to 7 of 7

Thread: Bug in Add process ??

  1. #1
    Join Date
    Oct 2002
    Posts
    161

    Bug in Add process ??

    When you add a record and you use the copy button to copy the content of the current record, and add some new additional data on the record, the clear button will only clear the newly typed data, it's impossible to clear the copied data witout having to go over each field and manually delete the data.

    The clear button must clear the whole record and not only the newly typed information.

  2. #2
    Join Date
    Oct 2002
    Posts
    93
    You're right. Thanks for reporting it.

    We'll look into it right away.

    John

  3. #3
    Join Date
    Oct 2002
    Posts
    933
    The trick is to hit the copy button again to "CLEAR". This is not an obvious way to implement the reset as you cannot find it.

    The decision is to make the copy non-sticky so after submit, it'll restore as blank ... note that the reset button reset to the original values. Copy create an original value by copying.


    FK

  4. #4
    Join Date
    Oct 2002
    Posts
    161
    Not sure what you mean Frank. Is the current behavior, the intended behavior? It's very ambiguous the way it is currently implementd, I don't need the copy button, is there a way to disable it?

  5. #5
    Join Date
    Oct 2002
    Posts
    933
    current behavior = yes
    intended behavior = yes (old way)
    very ambiguous = yes
    no good = yes
    disable and other solution = see below

    Soltuion -

    AddCopy is now non-sticky. It only executes upon clicking Copy and it'll go away in any other clicks (next, prev, index etc..) - except clear which is a reset. Copy button still toggles the copy and blanking. Now you can disable the button via the newly added parameter dbButtonsOnOff="AddCopy=false"

    So, you should have all the choices... look for >= (Oct 24) release.


    FK

  6. #6
    Join Date
    Oct 2002
    Posts
    161
    Thanks Frank, I'm really impressed for all your quick resolutions and fixes.

  7. #7
    Join Date
    Oct 2002
    Posts
    933
    The entire ASP-db is like this since day 1 and it is kind of unique. The features are proposed, discovered or demanded by the customers and if it is generic it'll be done immediately. Our experience is that majority of the proposal are good as customer usually do not have time to "fool around" with fancy but useless features. The only thing we have to watch out is to draw the watch the line between tool and application and not cross that.

    Frank

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •