Making an Input Form without showing all records

  • Thread starter Thread starter David P.
  • Start date Start date
D

David P.

I have a form that I want to use for inputting new records
only. Right now the form shows all records from the table
it is linked to, but I would like it just to be blank when
opened so a user can just add a record to it. How is this
done?

Thanks Dave
 
On the form's properties list look for an option called "Data Entry."
Set that to "Yes" and save the form.
Any time you open the form it will open to a new blank record and not allow you to view past records
already entered into the table.
 
Set the Data Entry property for the form to Yes. You'll find it on the Data
tab of the properties window.
 
I'm sorry, I want to do the same thing, but I can't seem
to find this option ?! Is it because I am working in
Access 2003 ? Or is there something else that I'm doing
wrong ?
I've tried it in the desing view just somewhere on the
page, and also per variable, but neither has a line 'Data
Entry' ???

Thank you,
Coja.

-----Original Message-----
On the form's properties list look for an option called "Data Entry."
Set that to "Yes" and save the form.
Any time you open the form it will open to a new blank
record and not allow you to view past records
 
coja said:
I'm sorry, I want to do the same thing, but I can't seem
to find this option ?! Is it because I am working in
Access 2003 ? Or is there something else that I'm doing
wrong ?
I've tried it in the desing view just somewhere on the
page, and also per variable, but neither has a line 'Data
Entry' ???

In design view of the form bring up the property sheet and make sure it is
displaying properties for "Form" not an object on the form, then select the
"Data" tab page. You will find the property there.
 
I did this, but when the user filters, all records show up again. Can
someone please look at my post "Problem with Filter" dated 9/4/04.
Brigitte P
 
I don't understand. If the data entry property is set to yes, then they
can't filter - there are no records to filter on.
 
Joan Wild said:
I don't understand. If the data entry property is set to yes, then they
can't filter - there are no records to filter on.

Actually when a form is opened in DataEntry mode all the user has to do is
"Remove all filters" and he is back at record 1 of n with all records available.
If you _really_ want to prevent seeing existing records you need a query like...

SELECT .... From .... WHERE 1 = 0
 
Yes, it's like Rick said. My user can apply a filter (and I want them to be
able to do so), and once they have what they need, they can remove the
filter, which brings them back to record one. I think the Data Entry yes
does the same as DoCmd.GoToRecord,,acNewRecord (or something like it), that
is, give only a new record but doesn't lock the recordset. I don't want to
lock the recordset, just have the user to go back to where they started
before the filter. I'm reposting below my post with the original question
and would very much appreciate help.
Original Post:
My user enters a seminar and then clicks a button to post this seminar to
the individual students attendance roster. The posting to the attendance
roster has only two fields: Student Social Security Number and Seminar
Number. The seminar number is filled in automatically as a default from the
previous form. The button that brings the user from the seminar form to the
attendance posting form sets the attendance posting form to new record. All
works well, except when the user applies a filter to look at some previous
postings and then clears the filter. After clearing the filter, the first
record of the whole recordset shows up.
However, we want the original screen, that is a blank field for the student
and the default value of the seminar number from the previous screen. How is
that done?
Thanks for any input.
Brigitte P.
 
I think I resolved my problem, probably not the most elegant way, but it'll
work. I added a button to the form that refreshes the form by running
DoCmd.GoToRecord , , acNewRec. This will reapply the default setting for the
seminar number, and the user is back where she needs to be. I noticed that
every time the filter was applied, the form reset the Date Entry property to
no. So now the button that brings the user to the form has the above command
line, as well as the refresh button, and the Data Entry property on the form
becomes irrelevant. Seems like an overkill, but it works in the A97 dbase
this user needs.
Furthermore, we allowed the filter option so she could delete a record if
she made a mistake. I'm removing the delete option on form level, but give
her a button where she can run a query showing just the records for the
seminar number on screen (either newly entered default from previous screen
or filtered records.) She then can delete her records on that level. I think
this will work better anyway and is a more safe procedure.
Thanks for your input, and also for any additional thought.
Brigitte P.
 
Rick said:
Actually when a form is opened in DataEntry mode all the user has to
do is "Remove all filters" and he is back at record 1 of n with all
records available. If you _really_ want to prevent seeing existing
records you need a query like...

I never realized that; probably because my users don't have access to the
remove filters command.

I usually set the recordsource to include WHERE False, and then offer
comboboxes/textboxes for them to search for the record they want. Then
build the SQL statement and apply it to the record source.
 
Back
Top