[AccessD] Subform => New Record first?

Blimey, another good idea. Nice one Reuben. Just goes to prove what a
flexible little baby Access is, or perhaps what flexible little minds are
needed to use it.

Anyway there's lots to go on Sander.

--
Andy Lacey
http://www.minstersystems.co.uk




--------- Original Message --------
From: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Subject: RE: [AccessD] Subform => New Record first?
Date: 24/10/03 15:11


Something I have done on several occasions to handle this very thing is to
basically ignore the subform as the solution, but rather put unbound fields
on the main form directly above the fields of the subform.

If you do not have the subform sunken you can't hardly tell they are not in
the subform (I usually leave mine sunken though).

The user inputs the new data into the unbound fields of the main form,
clicks an add button. You validate the data, write the data to the table
and requery the subform. And if that record needs to be at the top then
just set the sort order accordingly.

Reuben Cummings
GFC, LLC
phone: 812.523.1017
email: reuben at gfconsultants.com

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Andy Lacey
> Sent: Friday, October 24, 2003 9:00 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Subform => New Record first?
>
>
> Sander
> I know what you mean. My users often don't like this either. The answer to
> your question is no (I think) but a workaround is to place a
> command button
> in the header called "Add New Record" or whatever and behind there put:
>
> DoCmd.GoToRecord , , acNewRec
>
> It still goes to the bottom of the list but at least the user doesn't have
> to scroll down.
>
> There is another technique which may work but depends on your data to an
> extent. If, say, the data your subform is bound to has a date
> created field,
> and if your user is happy to see the data in desc order of date (ie newest
> at the top), then you can do the following:
>
> DoCmd.GoToRecord , , acNewRec
> me!DateField=Now()
> me.requery
>
> This will add the new record with the latest date then the
> requery will sort
> it to the top. Doesn't always suit, but can sometimes be effective.
>
> --
> Andy Lacey
> http://www.minstersystems.co.uk
>
>
>
>
> --------- Original Message --------
> From: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> To: "Acces User Group" <accessd at databaseadvisors.com>
> Subject: [AccessD] Subform => New Record first?
> Date: 24/10/03 13:37
>
>
> Hi group,
>
> I've got a subform. When I scroll through the records
> it is possible to add a record. However I first have
> to tab through all records (or use the scrollbar).
>
> Is it possible to have the new line (to insert a new
> record) appear on top (as the first line)?
>
> So you see an empty line and below it are all
> detailrecords.
>
> Hope this makes sence.
>
> TIA
>
> SD
>

________________________________________________
Message sent using UebiMiau 2.7.2