Adding new record in continuous form appears to produce records

[Catriona]

I am developing an Access application where users insert bill records
for an electricity account by clicking on a new button. The required
workflow is
1) New button clicked
2) New record appears with some field populated per defaults for
account and some based on previous records - eg dates
3) Save button clicked
4) Record validated and saved if it passes validation.

I have three issues as follows

1) I am using a subform with a continuous form view. The problem is
that when a new record is added, as soon as default values for fields
are entered, a duplicate record appears which I don't want. I know that
it has something to do with allowadditions but I am confused how to
incorporate this.

2) I also want the new record to appear at the end of the record list
for that account with all the other records showing. I have used the
data entry property, but it sets the focus on the first record and the
user needs to scroll to the end.

3) What is the best way to keep the user on the editted/new record
until they save or cancel?

Thanks in advance.

[Bas Cost Budde]

Catriona schreef:

I am developing an Access application where users insert bill records
for an electricity account by clicking on a new button. The required
workflow is
1) New button clicked
2) New record appears with some field populated per defaults for
account and some based on previous records - eg dates
3) Save button clicked
4) Record validated and saved if it passes validation.

I have three issues as follows

1) I am using a subform with a continuous form view. The problem is
that when a new record is added, as soon as default values for fields
are entered, a duplicate record appears which I don't want. I know that
it has something to do with allowadditions but I am confused how to
incorporate this.

Reading this as: as soon as you start entering data in the visible
record, Access displays the next new record below. Hmm... that is pretty
default behavior. Switched off by disallowing additions, but you do want
to enter data in the first place.

2) I also want the new record to appear at the end of the record list
for that account with all the other records showing. I have used the
data entry property, but it sets the focus on the first record and the
user needs to scroll to the end.

Answering these two questions in one. I advise you set AllowAdditions
for this form to False, and have the user enter a new record by means of
a button (which you must wire to insert the new record, and issue a
docmd.gotorecor d to it)

3) What is the best way to keep the user on the editted/new record
until they save or cancel?

Um... how about an extra field, presumably a boolean, that defaults to
false; and a table validation rule that states that this field must be
true? You can always cancel the entry by pressing Escape, if that's okay
with you; and if you want to save, use another button, that first puts a
True in our hidden field, and saves the record consequently.

I hope it makes sense! And if it doesn't, be sure to ask.
--
Bas Cost Budde
Holland