Changing Order in a table

Is it possible to have the first row of a table show the "blank record
line" instead of the first record. That way when people enter into
that table they don't have to scroll down to the end to insert a new
entry into the table.

They should not be entering data directly into a table. That's what forms
are for. In a table there is no way to do what you seek. In a form there
are a number of options, including seeing just one record at a time.

"Lisa" wrote in message
...
Is it possible to have the first row of a table show the "blank record
line" instead of the first record. That way when people enter into
that table they don't have to scroll down to the end to insert a new
entry into the table.

Do not have anyone entering data directly into the table.

Use a form. You can set a form's property set to Data Entry - Yes and it
opens to a new blank record. But it will only be for entry, no reading.

"Lisa" wrote:

Is it possible to have the first row of a table show the "blank record
line" instead of the first record. That way when people enter into
that table they don't have to scroll down to the end to insert a new
entry into the table.

On Apr 27, 12:41*pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:
They should not be entering data directly into a table. *That's what forms
are for. *In a table there is no way to do what you seek. *In a form there
are a number of options, including seeing just one record at a time.

"Lisa" wrote in message

...



Is it possible to have the first row of a table show the "blank record
line" instead of the first record. *That way when people enter into
that table they don't have to scroll down to the end to insert a new
entry into the table.- Hide quoted text -

- Show quoted text -

Sorry I wasn't clear. That table is a subform on a form. So when
they open the form and find that table to enter data into I want the
first line blank so they don't have to scroll to the bottom.
Otherwise, there are daily entries they have to scroll through to get
to the bottom of the table. W

One thing you can do is to make a single form with its Data Entry property
set to Yes. This means it can by used only for adding records, and for
viewing records added in the current session. You can prevent record
navigation for the most part by removing the navigation buttons. I will
call this form sfrmAdd.

Copy sfrmAdd as sfrmView. Change the Default View to Continuous, and Data
Entry to No. You can set Allow Additions to No to prevent using this form
to add new records, and to avoid the blank row that normally appears on a
continuous form. Set Allow Edits and Allow Deletions as needed for your
situation. Make it tall enough to show several records.

Add sfrmAdd as a subform, and sfrmView as another subform just below it. I
will call the subform controls (the "boxes" in which the subforms are
contained on the form) fsubAdd and fsubView. You can size the subforms so
they look like one continuous form, particularly if neither has a border.

sfrmAdd can have the table as its Record Source. sfrmAdd can have a query
based on the table as its Record Source, sorted as you would like. In the
After Update event of sfrmAdd:

Forms!MainFormName!fsubView.Form.Requery

When I have done this I have the users tab out of the last field to go to a
new record, but you could use a command button if you prefer. In any case,
requery in the After Update event as described. The just-added item in
sfrmAdd will show up in the continuous form.

"Lisa" wrote in message
...
On Apr 27, 12:41 pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:
They should not be entering data directly into a table. That's what forms
are for. In a table there is no way to do what you seek. In a form there
are a number of options, including seeing just one record at a time.

"Lisa" wrote in message

...



Is it possible to have the first row of a table show the "blank record
line" instead of the first record. That way when people enter into
that table they don't have to scroll down to the end to insert a new
entry into the table.- Hide quoted text -

- Show quoted text -

Sorry I wasn't clear. That table is a subform on a form. So when
they open the form and find that table to enter data into I want the
first line blank so they don't have to scroll to the bottom.
Otherwise, there are daily entries they have to scroll through to get
to the bottom of the table. W

On Apr 27, 2:29*pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:
One thing you can do is to make a single form with its Data Entry property
set to Yes. *This means it can by used only for adding records, and for
viewing records added in the current session. *You can prevent record
navigation for the most part by removing the navigation buttons. *I will
call this form sfrmAdd.

Copy sfrmAdd as sfrmView. *Change the Default View to Continuous, and Data
Entry to No. *You can set Allow Additions to No to prevent using this form
to add new records, and to avoid the blank row that normally appears on a
continuous form. *Set Allow Edits and Allow Deletions as needed for your
situation. *Make it tall enough to show several records.

Add sfrmAdd as a subform, and sfrmView as another subform just below it. *I
will call the subform controls (the "boxes" in which the subforms are
contained on the form) fsubAdd and fsubView. *You can size the subforms so
they look like one continuous form, particularly if neither has a border.

sfrmAdd can have the table as its Record Source. *sfrmAdd can have a query
based on the table as its Record Source, sorted as you would like. *In the
After Update event of sfrmAdd:

Forms!MainFormName!fsubView.Form.Requery

When I have done this I have the users tab out of the last field to go to a
new record, but you could use a command button if you prefer. *In any case,
requery in the After Update event as described. *The just-added item in
sfrmAdd will show up in the continuous form.

"Lisa" wrote in message

...
On Apr 27, 12:41 pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:





They should not be entering data directly into a table. That's what forms
are for. In a table there is no way to do what you seek. In a form there
are a number of options, including seeing just one record at a time.

"Lisa" wrote in message

....

Is it possible to have the first row of a table show the "blank record
line" instead of the first record. That way when people enter into
that table they don't have to scroll down to the end to insert a new
entry into the table.- Hide quoted text -

- Show quoted text -

Sorry I wasn't clear. *That table is a subform on a form. *So when
they open the form and find that table to enter data into I want the
first line blank so they don't have to scroll to the bottom.
Otherwise, there are daily entries they have to scroll through to get
to the bottom of the table. *W- Hide quoted text -

- Show quoted text -

Great suggestion Bruce. There are so many tricks to learn in Access.

I followed every step and the only problem I have is the after update
event. Here is the code and it does not work. The
frm_NewPatientEntry is the main form where the fsub_nursedatesview is
located. Is this correct? Did I miss something? When I make an
entry now I get an error after I tab out of the field.

Forms!frm_NewPatientEntry!fsub_nursedatesview.Form .Requery

What error is that?

"Lisa" wrote in message
...
On Apr 27, 2:29 pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:
One thing you can do is to make a single form with its Data Entry property
set to Yes. This means it can by used only for adding records, and for
viewing records added in the current session. You can prevent record
navigation for the most part by removing the navigation buttons. I will
call this form sfrmAdd.

Copy sfrmAdd as sfrmView. Change the Default View to Continuous, and Data
Entry to No. You can set Allow Additions to No to prevent using this form
to add new records, and to avoid the blank row that normally appears on a
continuous form. Set Allow Edits and Allow Deletions as needed for your
situation. Make it tall enough to show several records.

Add sfrmAdd as a subform, and sfrmView as another subform just below it. I
will call the subform controls (the "boxes" in which the subforms are
contained on the form) fsubAdd and fsubView. You can size the subforms so
they look like one continuous form, particularly if neither has a border.

sfrmAdd can have the table as its Record Source. sfrmAdd can have a query
based on the table as its Record Source, sorted as you would like. In the
After Update event of sfrmAdd:

Forms!MainFormName!fsubView.Form.Requery

When I have done this I have the users tab out of the last field to go to
a
new record, but you could use a command button if you prefer. In any case,
requery in the After Update event as described. The just-added item in
sfrmAdd will show up in the continuous form.

"Lisa" wrote in message

...
On Apr 27, 12:41 pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:





They should not be entering data directly into a table. That's what
forms
are for. In a table there is no way to do what you seek. In a form there
are a number of options, including seeing just one record at a time.

"Lisa" wrote in message

...

Is it possible to have the first row of a table show the "blank record
line" instead of the first record. That way when people enter into
that table they don't have to scroll down to the end to insert a new
entry into the table.- Hide quoted text -

- Show quoted text -

Sorry I wasn't clear. That table is a subform on a form. So when
they open the form and find that table to enter data into I want the
first line blank so they don't have to scroll to the bottom.
Otherwise, there are daily entries they have to scroll through to get
to the bottom of the table. W- Hide quoted text -

- Show quoted text -

Great suggestion Bruce. There are so many tricks to learn in Access.

I followed every step and the only problem I have is the after update
event. Here is the code and it does not work. The
frm_NewPatientEntry is the main form where the fsub_nursedatesview is
located. Is this correct? Did I miss something? When I make an
entry now I get an error after I tab out of the field.

Forms!frm_NewPatientEntry!fsub_nursedatesview.Form .Requery

On Apr 28, 6:03*am, "BruceM" bamoob_at_yawhodotcalm.not wrote:
What error is that?

"Lisa" wrote in message

...
On Apr 27, 2:29 pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:





One thing you can do is to make a single form with its Data Entry property
set to Yes. This means it can by used only for adding records, and for
viewing records added in the current session. You can prevent record
navigation for the most part by removing the navigation buttons. I will
call this form sfrmAdd.

Copy sfrmAdd as sfrmView. Change the Default View to Continuous, and Data
Entry to No. You can set Allow Additions to No to prevent using this form
to add new records, and to avoid the blank row that normally appears on a
continuous form. Set Allow Edits and Allow Deletions as needed for your
situation. Make it tall enough to show several records.

Add sfrmAdd as a subform, and sfrmView as another subform just below it.. I
will call the subform controls (the "boxes" in which the subforms are
contained on the form) fsubAdd and fsubView. You can size the subforms so
they look like one continuous form, particularly if neither has a border.

Is the form open, and are you absolutely sure everything is spelled
correctly?

"Lisa" wrote in message
...
On Apr 28, 6:03 am, "BruceM" bamoob_at_yawhodotcalm.not wrote:
What error is that?

"Lisa" wrote in message

...
On Apr 27, 2:29 pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:





One thing you can do is to make a single form with its Data Entry
property
set to Yes. This means it can by used only for adding records, and for
viewing records added in the current session. You can prevent record
navigation for the most part by removing the navigation buttons. I will
call this form sfrmAdd.

Copy sfrmAdd as sfrmView. Change the Default View to Continuous, and
Data
Entry to No. You can set Allow Additions to No to prevent using this
form
to add new records, and to avoid the blank row that normally appears on
a
continuous form. Set Allow Edits and Allow Deletions as needed for your
situation. Make it tall enough to show several records.

Add sfrmAdd as a subform, and sfrmView as another subform just below it.
I
will call the subform controls (the "boxes" in which the subforms are
contained on the form) fsubAdd and fsubView. You can size the subforms
so
they look like one continuous form, particularly if neither has a
border.

sfrmAdd can have the table as its Record Source. sfrmAdd can have a
query
based on the table as its Record Source, sorted as you would like. In
the
After Update event of sfrmAdd:

Forms!MainFormName!fsubView.Form.Requery

When I have done this I have the users tab out of the last field to go
to
a
new record, but you could use a command button if you prefer. In any
case,
requery in the After Update event as described. The just-added item in
sfrmAdd will show up in the continuous form.

"Lisa" wrote in message

...
On Apr 27, 12:41 pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:

They should not be entering data directly into a table. That's what
forms
are for. In a table there is no way to do what you seek. In a form
there
are a number of options, including seeing just one record at a time.

"Lisa" wrote in message

...

Is it possible to have the first row of a table show the "blank
record
line" instead of the first record. That way when people enter into
that table they don't have to scroll down to the end to insert a new
entry into the table.- Hide quoted text -

- Show quoted text -

Sorry I wasn't clear. That table is a subform on a form. So when
they open the form and find that table to enter data into I want the
first line blank so they don't have to scroll to the bottom.
Otherwise, there are daily entries they have to scroll through to get
to the bottom of the table. W- Hide quoted text -

- Show quoted text -

Great suggestion Bruce. There are so many tricks to learn in Access.

I followed every step and the only problem I have is the after update
event. Here is the code and it does not work. The
frm_NewPatientEntry is the main form where the fsub_nursedatesview is
located. Is this correct? Did I miss something? When I make an
entry now I get an error after I tab out of the field.

Forms!frm_NewPatientEntry!fsub_nursedatesview.Form .Requery- Hide quoted
text -

- Show quoted text -

It says it can't find the form name.

On Apr 28, 10:46*am, "BruceM" bamoob_at_yawhodotcalm.not wrote:
Is the form open, and are you absolutely sure everything is spelled
correctly?

"Lisa" wrote in message

...
On Apr 28, 6:03 am, "BruceM" bamoob_at_yawhodotcalm.not wrote:





What error is that?

"Lisa" wrote in message

...
On Apr 27, 2:29 pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:

One thing you can do is to make a single form with its Data Entry
property
set to Yes. This means it can by used only for adding records, and for
viewing records added in the current session. You can prevent record
navigation for the most part by removing the navigation buttons. I will
call this form sfrmAdd.

Copy sfrmAdd as sfrmView. Change the Default View to Continuous, and
Data
Entry to No. You can set Allow Additions to No to prevent using this
form
to add new records, and to avoid the blank row that normally appears on
a
continuous form. Set Allow Edits and Allow Deletions as needed for your
situation. Make it tall enough to show several records.

Add sfrmAdd as a subform, and sfrmView as another subform just below it.
I
will call the subform controls (the "boxes" in which the subforms are
contained on the form) fsubAdd and fsubView. You can size the subforms
so
they look like one continuous form, particularly if neither has a
border.

sfrmAdd can have the table as its Record Source. sfrmAdd can have a
query
based on the table as its Record Source, sorted as you would like. In
the
After Update event of sfrmAdd:

Forms!MainFormName!fsubView.Form.Requery

When I have done this I have the users tab out of the last field to go
to
a
new record, but you could use a command button if you prefer. In any
case,
requery in the After Update event as described. The just-added item in
sfrmAdd will show up in the continuous form.

"Lisa" wrote in message

....
On Apr 27, 12:41 pm, "BruceM" bamoob_at_yawhodotcalm.not wrote:

They should not be entering data directly into a table. That's what
forms
are for. In a table there is no way to do what you seek. In a form
there
are a number of options, including seeing just one record at a time..

"Lisa" wrote in message

...

Is it possible to have the first row of a table show the "blank
record
line" instead of the first record. That way when people enter into
that table they don't have to scroll down to the end to insert a new
entry into the table.- Hide quoted text -

- Show quoted text -

Sorry I wasn't clear. That table is a subform on a form. So when
they open the form and find that table to enter data into I want the
first line blank so they don't have to scroll to the bottom.
Otherwise, there are daily entries they have to scroll through to get
to the bottom of the table. W- Hide quoted text -

- Show quoted text -

Great suggestion Bruce. There are so many tricks to learn in Access.

I followed every step and the only problem I have is the after update
event. Here is the code and it does not work. The
frm_NewPatientEntry is the main form where the fsub_nursedatesview is
located. Is this correct? Did I miss something? When I make an
entry now I get an error after I tab out of the field.

Forms!frm_NewPatientEntry!fsub_nursedatesview.Form .Requery- Hide quoted
text -

- Show quoted text -

It says it can't find the form name.- Hide quoted text -

- Show quoted text -

Yes. The main form I am using has both subforms on it. The
dataeentry form and the view form. The main form is called frm
NewPatientEntry. There is no underscore in the actual name but I had
to add it in the code. I even changed the name of the main form to
the data entry form thinking I was supposed to use that form and I get
the same error. It can't find the form name. Any ideas?