Re: Add button acting as Save button on first use

On Tuesday 20 September 2005 16:41, Joshua Brickel wrote:
>  Hi,
>
> I will try to be clearer...
>
>    1. I created a table called "test", it had two columns.  One is an
>       index called "id" that is declared the primary key.  The second is
>       a VARCHAR field called "name".
>    2. Next I created a Form using the "Create Form With..." with the
>       following atributes:
>           * A field to fill in a "name"
>           * The "Add", "Save", "Delete" buttons were added
>           * the MiniNavi Bar is activated
>    3. I then used the form to add two names into the table "test."
>    4. I then closed the form.
>    5. I then reopened the form.  At this point I noticed that the form
>       shows the first item in table "test" and the MiniNavi Bar indeed
>       shows "Record 1 of 2"
>    6. I then change the name in the text filed and press the button "Add".
>
> What I would expect at this point is that I would have added a new entry
> to the bottom of the table.  However what occurs is that Record #1 is
> overwritten.
>
>    7. After that the MiniNavi Bar skipps over to say "New Record"

OK, here's what happens.

You open the form and it starts on record 1. You make a fiew changes, then 
click the Add button. This means "add a new record" rather than "add *as* a 
new record". So rekall opens up a new empty record in the form. *BUT* it sees 
that you have changed the current record, so it saves that first.

Rekall 2.3.x (2.4.0 coming soon :) has a "saveAsNewRecord" method which would 
do what you want, but its not in 2.2.x


>
> If I add another entry at this point it will now add this new entry to
> the end of the table.
>
> So in summary, what I would expect is that if I use the "add" button
> from in step 6 that a new entry would be added to the table "test".  If
> I wanted the entry overwritten I would have pushed on the "save" button.
>
> If between steps 5 and 6 above I pressed on "add" then the form skips to
> the end of the list, but does not actually add a record.
>
> If I am still not clear enough, please let me know in which areas
> (steps) I should be more specific.
>
> Regards,
>
> Joshua
>
> Mike Richardson wrote:
> >On Tuesday 20 September 2005 14:31, Joshua Brickel wrote:
> >>Hi,
> >>
> >>I have begun to experiment with using Rekall to design front ends to the
> >>MySQL database.  I hve been having a problem with the "add" button when
> >>creating a form.
> >>
> >>The problem is that it would appear that the add button should "add" a
> >>new entry into the database.  However the first time the "add" button is
> >>pressed it actually to replaces the first entry in the list.  After that
> >>an additional entries are actually added to the dB.  The add button
> >>should NOT replace the first entry.
> >
> >Sorry, not quite sure what you mean, could you elaborate a bit (a
> > blow-by-blow account :)
> >
> >Ta
> >Mike
> >
> >>In fact the Rekall system seems to treat the first one as if I had
> >>pressed "save" instead of "add."
> >>
> >>I am using Rekall ver.  2.2.3, with MySQL ver. 4.0.24 running on a
> >>Debian Linux system.
> >>
> >>Has this bug been reported by anyone else?  Does anyone have a work
> >>around?  Also is there a place (mailing list, website, etc.) for me to
> >>report the bug.
> >>
> >>Regards,
> >>
> >>Joshua
> >>
> >>
> >>
> >>_______________________________________________
> >>Rekall-devel mailing list
> >>[email protected]
> >>http://www.mailman.a-i-s.co.uk/cgi-bin/mailman/listinfo/rekall-devel

-- 
Regards
Mike

http://www.rekallrevealed.org
*THE* GPL/Open Source database front end for Linux and Windows.