Opening New Form and Closing Another Causes Error 2467 on some computers

duthiedon

Donner
Local time
Yesterday, 23:26
Joined
Dec 27, 2007
Messages
60
I have never seen this error before nor can I recreate it on my computer. We currently use Access 2007. Basically, I have forms that when the user finishes entering information, another form will open and then close the current one. It's pretty simple, but on one users computer it's causing consistently this error:

Error 2467 - Error Description - The Expression you entered refers to an object that is close or doesn't exist.

Never saw this error until recently. There's 2 types of events either via a macro or via VBA:

Macro example:

Action & Arguments
-------------------
RunCommand SaveRecord
OpenForm frm:Vendor_Details, Form, , ="[ID-Vendor]=" & [ID-Vendor], , Normal
Close Form, Frm:VendorManage, Prompt

VBA example:
'if a group is assigned then log the user in else close the application.
If isGrpAssigned <> 0 Then
gbl_User = Me.cboEmployee.Value ' pass the username to the global user variable
DoCmd.OpenForm "frm_MainForm" ' Open the main form
DoCmd.Close acForm, "frmLogon" 'close the log on form
Else
.....


Has anyone seen this before? Any resolutions?
 
This is a split database FE/BE and every user has their own copy of the FE on their PC?

Is there a subform involved? I did some searching and many hits identify issue with subform not completely loaded????
 
Last edited:
Yes it is a split database, but both parts are on the server. I can still recreate the issue with it on my USB key using their computer. There are no subforms and the error is consistent no matter what form or how complex it is. It's the simple close of the form itself.
 
Thanks jdraw, spent quite a bit of time researching and haven't found an answer. It's a strange one :) I will keep digging...
 
For those interested, I have converted all macros into VBA, rebuilt the database by importing all elements, and still no luck :( We are all using the same version of Windows 7 and Office 2007 as well. Any further suggestions would be greatly appreciated...
 
For those interested, I resolved the issue finally, had a slight error in one of the macros I converted to VBA. It appears that the solution was removing every single macro in the database and converting them into VBA.
 

Users who are viewing this thread

Back
Top Bottom