Runtime error 2467 on some setups, not others

[PaulA]

Greetings, all,

Here's the lowdown: I have a split database as Access 2003 files accessed through Access 2010. Both files are stored on a server with the FE file being accessed on that server, not on individual hard drives.

I am now getting an runtime error 2467 "the expression you entered refers to an object that is closed or doesn't exists". I am then directed to debug some code which does not appear to be problematic. Then names are all correct.

This only happens at one location and all users at this location get this error. I am not able to replicate this error where I am where I don't have the same network setup, although I do have duplicate files on a different server.

Below is the code. Since I can't replicate, the trigger line is bold and red.

I also haven't supplied code on this forum and wasn't sure how to put the code in a separate window. Any help is appreciated.

Thanks.

Paul

code:
Private Sub Form_Open(Cancel As Integer)

Me.cboPatientLookup = ""

Me.frmIndClinicalUtilTracksub.Form.DataEntry = True
Me.frmGroupProgressNotesub.Form.DataEntry = True
Me.frmIndNarrativeNotesub.Form.DataEntry = True
Me.frmDaily1on1sub.Form.DataEntry = True
DoCmd.GoToRecord , , acNewRec

 

[JHB]

Here's the lowdown: I have a split database as Access 2003 files accessed through Access 2010. Both files are stored on a server with the FE file being accessed on that server, not on individual hard drives.

Why did you split the database then, if you don't use the benefits it provides?

I am now getting an runtime error 2467 "the expression you entered refers to an object that is closed or doesn't exists". I am then directed to debug some code which does not appear to be problematic. Then names are all correct.

Try to place the code in the form's load event instead or maybe a DoEvents can solve the problem.
The problem is sometimes the sub form isn't loaded at the time the form's open event trigger, therefore it is unknown, but when the code stops with an error it gives the system/program time to load the sub form and you'll not recognize it isn't loaded, because at that time you start to debug it is got loaded.

 

[PaulA]

Thanks for your response. I'll try your suggestions.

In answer to your question, other locations with the database do use the FE on their hard drive. We just don't at this location. Also, it's easier to make modifications to the FE and plugging that application in without interrupting data entry.

We may go to putting the FE on the individual hard drives but that set up didn't seem to impact this particular problem (I tested it). It also was just for this particular file and not for an earlier version of the same application.

 

[JHB]

Thanks for your response. I'll try your suggestions.

Did you try it?

 

[PaulA]

Yes, I did. I put the code in the load event. It seems to have done the trick. Thanks for the suggestion.