runtime error 2718?

[Savvoulidis Iordanis]

I have a client that complaints about a runtime error 2718 in my Access app.
This error occurs in arbitrary times, usually once a day (the app is on, the
whole day). Although the app doesn't crash after the error message is closed,
as my client says, the subforms tend to display to many copies of the records
previously displayed and also they flash like if a refresh was being executed
with F9 key down continously. So he must stop and start the app again.

I haven't been able to reproduce that error, so I'm asking for your help, if
somebody has seen it before.

There are only 2 sepatate users running the app, through MS Terminal Service
sessions (I don't think TS causes the problem though). The app is a MS Access
2003 Front End .MDE and MS access 2003 .MDB back end. Each Front End .MDE is
inside a separate folder for each user. Both are accessing the same .MDB.

My research for error 2718 in Google didn't help at all.
Any help is appreciated.
TIA

 

[dymondjack]

Application-defined or object-defined error

This is the description for error 2718. Generally it pops up when
particular code is pointed to a control (or any object) that can't be found.

By the sounds of it, this is happening on a requery for a subform (the code
is looping, trying to requery the subform recordsource maybe?). Do you have
an SQL 'rebuild' function on a control change somewhere on the mainform? For
example, if control X changes, it rebuilds the SQL string based on other
controls on the mainform, and then updates the subform? If that's the case,
then it may be a control reference is off and is throwing the error.
Something along those lines anyway.

2718 is a fairly common error, and could be any number of things, but that's
where I'd start.

You can (and maybe should), redistribute another copy of the frontend to the
client, with included line numbers in the VBA code, and include the Erl()
function in your handler. If your client can give you the line number, it
should point you to the exact line that the code is breaking on, making
debugging much easier.

hth
--
Jack Leach
www.tristatemachine.com

- "Success is the ability to go from one failure to another with no loss of
enthusiasm." - Sir Winston Churchill