Re: When typing stops, record saves automatically
From: Paul (Paul_at_discussions.microsoft.com)
Date: 09/21/04
- Next message: GH: "Re: combo box selection doesn't remain on the record"
- Previous message: Paul B.: "DoCmd.FindRecord help needed"
- In reply to: Dirk Goldgar: "Re: When typing stops, record saves automatically"
- Next in thread: Dirk Goldgar: "Re: When typing stops, record saves automatically"
- Reply: Dirk Goldgar: "Re: When typing stops, record saves automatically"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 21 Sep 2004 08:31:03 -0700
Thanks for your willingness to assist. I have zipped it up and emailed it to
you.
"Dirk Goldgar" wrote:
> "Paul" <Paul@discussions.microsoft.com> wrote in message
> news:0C1C5FA5-F4A4-4BC7-B4AA-CA4E354DA193@microsoft.com
> > After playing around with it a bit, including building a brand new
> > form from the ground up to do the same thing, I've found at least
> > what is triggering this to occur, but I still don't know why.
> >
> > First, a quick overview of the application...basically from a
> > dashboard, the end-user clicks a command button to 'Update Existing
> > Project'. This opens the 'Available Projects' form, where after
> > selecting the 'Project Owner' from a combo box, a list box is
> > automatically populated with the Projects associated to the 'Project
> > Owner'. Next, via a double-click or 'Open' command button, the
> > record selected within the list box is populated in another form, the
> > 'Project_Update' form. This form lists the details of the Project
> > and includes a list box showing all the updates that have been added
> > in the past. The end-user can then click a command button to 'Add
> > Update'. This opens the form/subform I'm having a problem with
> > ('Update Project Details' form).
> >
> > The link between this form and its subform is a 'Project ID' field -
> > this allows the two to synch with eachother and works fine. The key
> > is the 'Project ID' on the main form is tied back to the previous
> > form as its control source (Forms![Project_Update]![Project ID] ). I
> > have to do this in order to reference and write the update to the
> > correct record in the Project table.
> >
> > Here is what I've found...if I DON'T link the 'Project ID' back to the
> > 'Project_Update' form, I can add an update without a problem...I can
> > type, pause, type, pause, type and it won't save until I close the
> > form.
> >
> > BUT, I can't select the 'Project ID', the system just picks the first
> > one available and the update goes to it. I don't want the end-user
> > to have to select the 'Project ID' from another Combo box since
> > they've already selected to add the update to a specific 'Project ID'
> > on the previous form.
> >
> > As soon as I change the control source of the 'Project ID' back to
> > look at the 'Project ID' on the 'Project_Update' form, the issue
> > resurfaces. I type a letter and if I stop, it instantly adds the
> > record to the database and clears the form for the next entry.
> >
> > Does any of this shed light? Thanks!
>
> Some light begins to dawn, but we don't have full illumination yet. You
> wrote:
>
> > The key
> > is the 'Project ID' on the main form is tied back to the previous
> > form as its control source (Forms![Project_Update]![Project ID] ).
>
> What *exactly* is in the controlsource of the main form's [Project ID]
> control? Is it
>
> =[Forms]![Project_Update]![Project ID]
>
> ? Or something else? Is there any code in the form that relates to
> this control? Is a Recalc being performed? Did you say there is no
> Timer event in the main form or subform? Is there a Timer event firing
> in the Project_Update form that does anything with this control?
>
> Would you be interested in sending me your database, to eliminate some
> of the back-and-forth questions and answers? It would have to be a
> cut-down copy of the database, containing only the elements necessary to
> demonstrate the problem, compacted and then zipped to less than 1MB in
> size (preferably much smaller). If you do, I'll have a look at it, time
> permitting. You can send it to the address derived by removing NO SPAM
> from the reply address of this message.
>
> --
> Dirk Goldgar, MS Access MVP
> www.datagnostics.com
>
> (please reply to the newsgroup)
>
>
>
- Next message: GH: "Re: combo box selection doesn't remain on the record"
- Previous message: Paul B.: "DoCmd.FindRecord help needed"
- In reply to: Dirk Goldgar: "Re: When typing stops, record saves automatically"
- Next in thread: Dirk Goldgar: "Re: When typing stops, record saves automatically"
- Reply: Dirk Goldgar: "Re: When typing stops, record saves automatically"
- Messages sorted by: [ date ] [ thread ]