[AccessD] Error 2455

Rocky Smolin rockysmolin2 at gmail.com
Sun Sep 26 00:10:14 CDT 2021


I think it must have something to do with timing or a buffer overflow.  Is
there a way to clear the keyboard buffer in VBA?  Maybe if I clearewd the
keyboard buffer after every move to a new record (in the Current event) it
might solve the problem?

r

On Sat, Sep 25, 2021 at 10:08 PM Paul Hartland via AccessD <
accessd at databaseadvisors.com> wrote:

> Ah ok, just thought the solution may have offered  possible idea.
>
> Paul
>
> On Sun, 26 Sep 2021, 03:48 Rocky Smolin, <rockysmolin2 at gmail.com> wrote:
>
> > Hadn't seen that Paul, but I don't think it pertains to my case. Got no
> > grandchildren in that form.
> >
> > r
> >
> > On Sat, Sep 25, 2021 at 5:32 PM Paul Hartland via AccessD <
> > accessd at databaseadvisors.com> wrote:
> >
> > > Did you come across this site when searching for solutions....
> > >
> > >
> > >
> >
> https://stackoverflow.com/questions/10401501/microsoft-access-runtime-error-2455-when-trying-to-access-grandchildren-forms-fr
> > >
> > > Paul
> > >
> > > On Sun, 26 Sep 2021, 01:23 Rocky Smolin, <rockysmolin2 at gmail.com>
> wrote:
> > >
> > > > Gustav:
> > > >
> > > > As I 'Next Record' through the recordset, it displays correctly
> Clients
> > > > that have no Persons associated with it.  If I look at the Client ID
> > > where
> > > > it blows up, 1) it blows up on difference Client records, and 2) when
> > > > selected from the combo box, that Client displays correctly. And in
> > these
> > > > tests the Client has Person records to display in the sub-form.
> > > >
> > > > I changed the form format to include Navigation buttons and as fast
> as
> > I
> > > > can click on the next record button, it never errors out. However,
> > when I
> > > > stop clicking the button, a few more records are accessed so I
> suppose
> > > > there are a few clicks in the buffer.
> > > >
> > > > Is it possible that my 'Next Record' routine is a problem?  It''s
> > pretty
> > > > simple code and I've been using it for years without a problem being
> > > > reported by any user:
> > > >
> > > > On Error GoTo IsIt2105:
> > > >
> > > >    DoCmd.GoToRecord , , acNext
> > > >    Exit Sub
> > > >
> > > > IsIt2105:
> > > > If Err.Number = 2105 Then Exit Sub
> > > >
> > > > MsgBox "Error: " & Err.Number & " - " & Err.Description
> > > >
> > > >
> > > > MsgBox "Error: " & Err.Number & " - " & Err.Description
> > > >
> > > >
> > > > Thanks for your help.
> > > >
> > > > Rocky
> > > >
> > > > On Sat, Sep 25, 2021 at 3:07 PM Gustav Brock via AccessD <
> > > > accessd at databaseadvisors.com> wrote:
> > > >
> > > > > Hi Rocky
> > > > >
> > > > > It sounds like one of the main records has no child records.
> > > > >
> > > > > /gustav
> > > > >
> > > > > -----Oprindelig meddelelse-----
> > > > > Fra: AccessD <accessd-bounces+gustav=
> cactus.dk at databaseadvisors.com>
> > > På
> > > > > vegne af Rocky Smolin
> > > > > Sendt: 25. september 2021 22:31
> > > > > Til: Access Developers discussion and problem solving <
> > > > > accessd at databaseadvisors.com>; Off Topic <
> > dba-ot at databaseadvisors.com>
> > > > > Emne: [AccessD] Error 2455
> > > > >
> > > > > Dear List(s):
> > > > >
> > > > > I have a form that has a 'next record button' that moves the bound
> > form
> > > > to
> > > > > the next record.  When it does that the Current event, which has a
> > > bunch
> > > > of
> > > > > code in it, runs.
> > > > >
> > > > > If the user toggles cycles the recordset with the Next Record
> button,
> > > it
> > > > > eventually errors out with an error 2455: You entered an expression
> > > that
> > > > > has an invalid reference to the property form/re;port.
> > > > >
> > > > > The line of code it errors is:
> > > > >
> > > > >  Me.sfrmClientPerson.Form.Section(acHeader).BackColor = 15263976
> > > > >
> > > > > It's part of the process of turning the form gray and disabling it
> if
> > > the
> > > > > client is inactive.  This line of code refers to a subform.
> > > > >
> > > > > I tried putting in a delay of one or two seconds at the top of the
> > > > current
> > > > > event, on the theory that maybe the subform references in that line
> > of
> > > > code
> > > > > is not finished loading yet.  DoEvents also was not effective.
> > > > >
> > > > > Any ideas on how to fix this? Other than telling the user not to
> > toggle
> > > > so
> > > > > fast through the records and use the Find button instead.
> > > > >
> > > > > MTIA
> > > > >
> > > > > Rocky
> > > > > --
> > > > > AccessD mailing list
> > > > > AccessD at databaseadvisors.com
> > > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > > Website: http://www.databaseadvisors.com
> > > > >
> > > > --
> > > > AccessD mailing list
> > > > AccessD at databaseadvisors.com
> > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > Website: http://www.databaseadvisors.com
> > > >
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


More information about the AccessD mailing list