Error 2467 but only in runtime...

  • Thread starter Thread starter Fred Boer
  • Start date Start date
F

Fred Boer

Hello!

Running Access 2002/Access 2002 runtime/Windows XP/98se...

I have an application which runs without error on the full version of Access
2002. However, if I run the application on a workstation as an MDE run-time
version, I get a 2467 error ("The expression you entered refers to an object
that is closed or doesn't exist..."). There is a main form and a hidden
subform. The problem lies with the subform. For some reason it doesn't load,
and the main form is supposed to pull a value from a control on the subform.

The application is split FE/BE. All computers use the same BE tables.

Some of the workstations have Access 2000. I can run the app as an MDB in
Access 2000 format, no problem...

I am stumped.... I don't know where to look...

Thanks!
Fred Boer

P.S. How the heck do you debug a runtime version? :(
 
Fred Boer said:
Hello!

Running Access 2002/Access 2002 runtime/Windows XP/98se...

I have an application which runs without error on the full version of
Access 2002. However, if I run the application on a workstation as an
MDE run-time version, I get a 2467 error ("The expression you entered
refers to an object that is closed or doesn't exist..."). There is a
main form and a hidden subform. The problem lies with the subform.
For some reason it doesn't load, and the main form is supposed to
pull a value from a control on the subform.

The application is split FE/BE. All computers use the same BE tables.

Some of the workstations have Access 2000. I can run the app as an
MDB in Access 2000 format, no problem...

I am stumped.... I don't know where to look...

Thanks!
Fred Boer

P.S. How the heck do you debug a runtime version? :(
Click to expand...

With great difficulty ... (and by inserting tracking code that logs the
state of the application at various control points).

Does the subform try to open anything in Design View? That won't work
in an MDE, of course. Is there code behind the subform? If so, you
might try (in a test copy of the app) deleting that completely, creating
an MDE, and seeing if that makes a difference. Is there anything
"special" about the subform? If you delete the subform and the code
that references it, can you make an MDE that runs without the error?
 
Hello, Dirk!
Does the subform try to open anything in Design View? That won't work
in an MDE, of course.
No...

Is there code behind the subform?
No...

Is there anything "special" about the subform?
Click to expand...

Well, I don't *think* so.. There is only 1 control, a textbox. I will append
at the end of this message the two queries involved in the subform...
If you delete the subform and the code that references it, can you make an
Click to expand...
MDE that runs without the error?

Yes... That's why I think it is the subform, and I strongly suspect that the
problem is with the queries, but since everything seems to work ok as an
MDB, I can't tell what is wrong with the MDE. I have tried running the MDE
on a number of computers, and I have also reinstalled the Access Runtime
files and tried that too, with no success.

Thanks for your help!

Fred


Saved Query:

SELECT Lb.Book_ID, Au.AuthorLastName & ", " & Au.AuthorFirstName & " " &
Au.AuthorMiddleName AS Author, Lb.Title, Lb.CopyNumber, Lb.NumberOfVolumes,
Lb.VolumeNumber, Lb.Dewey, Lo.Location, BA.PrimaryAuthor
FROM Tbl_Location AS Lo INNER JOIN (Tbl_Library AS Lb INNER JOIN (Tbl_Author
AS Au INNER JOIN Tbl_BookAuthor AS BA ON Au.Author_ID = BA.Author_ID) ON
Lb.Book_ID = BA.Book_ID) ON Lo.Location_ID = Lb.Location_ID
WHERE (((BA.PrimaryAuthor)=-1));

Recordsource of Subform:

SELECT Qry_LabelSpine.Book_ID, UCase(Left([Qry_LabelSpine].[Author],3)) AS
Cutter
FROM Qry_LabelSpine
WHERE (((Qry_LabelSpine.PrimaryAuthor)=-1));
 
Fred Boer said:
Hello, Dirk!
Does the subform try to open anything in Design View? That won't
work
in an MDE, of course.
No...

Is there code behind the subform?
No...

Is there anything "special" about the subform?
Click to expand...

Well, I don't *think* so.. There is only 1 control, a textbox. I will
append at the end of this message the two queries involved in the
subform...
If you delete the subform and the code that references it, can you
make an
Click to expand...
MDE that runs without the error?

Yes... That's why I think it is the subform, and I strongly suspect
that the problem is with the queries, but since everything seems to
work ok as an MDB, I can't tell what is wrong with the MDE. I have
tried running the MDE on a number of computers, and I have also
reinstalled the Access Runtime files and tried that too, with no
success.

Thanks for your help!

Fred


Saved Query:

SELECT Lb.Book_ID, Au.AuthorLastName & ", " & Au.AuthorFirstName & "
" & Au.AuthorMiddleName AS Author, Lb.Title, Lb.CopyNumber,
Lb.NumberOfVolumes, Lb.VolumeNumber, Lb.Dewey, Lo.Location,
BA.PrimaryAuthor
FROM Tbl_Location AS Lo INNER JOIN (Tbl_Library AS Lb INNER JOIN
(Tbl_Author AS Au INNER JOIN Tbl_BookAuthor AS BA ON Au.Author_ID =
BA.Author_ID) ON Lb.Book_ID = BA.Book_ID) ON Lo.Location_ID =
Lb.Location_ID
WHERE (((BA.PrimaryAuthor)=-1));

Recordsource of Subform:

SELECT Qry_LabelSpine.Book_ID,
UCase(Left([Qry_LabelSpine].[Author],3)) AS Cutter
FROM Qry_LabelSpine
WHERE (((Qry_LabelSpine.PrimaryAuthor)=-1));
Click to expand...

Hmm I don't see anything wrong with those offhand. If you select those
query results into tables and use the tables in place of the queries,
does it make a difference?

Does the main form do anything with the properties of the subform
control, such as change the Source Object or the Link Master/Child
Fields properties?

Does the MDE fail no matter where you run it? Have you verified that
there are no broken references?

I have to go out now for the evening. If you're still stuck, see if you
can make a cut-down, minimal version of the database that has the same
problem, then compact it, zip it, and send it to me.
 
Dear Dirk:
Hmm I don't see anything wrong with those offhand. If you select those
query results into tables and use the tables in place of the queries,
does it make a difference?
Click to expand...

I will try this tomorrow...
Does the main form do anything with the properties of the subform
control, such as change the Source Object or the Link Master/Child
Fields properties?
No...

Does the MDE fail no matter where you run it? Have you verified that
there are no broken references?
Yes...

I have to go out now for the evening. If you're still stuck, see if you
can make a cut-down, minimal version of the database that has the same
problem, then compact it, zip it, and send it to me.
Click to expand...

Thanks for the offer, Dirk. However, I'll try your suggestion about using
tables and double check the references first, and give it another shot
tomorrow. If I still come up empty, you'll hear from me! <g>

Thanks!
Fred
 
Ok, well I have it fixed... As you suspected, Dirk, it was a references
problem. I *had* been careful to check the references when developing the
form, which I do in the default Access 2000 file format. These were always
correct. What I *didn't* do, was check them after conversion to the Access
2002 file format (before creating the MDE). The conversion process was
adding a new reference.

A2K:

Visual Basic for Applications
Microsoft Access 10.0 Object Library
Microsoft DAO 3.6 Object Library

A2K2

Visual Basic for Applications
Microsoft Access 10.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft Office XP Web Components

Removing this last reference solved the problem. So it was my fault, but it
just didn't occur to me that references would be changed on conversion...

Thanks for your help! You put me on the right track...

Fred




Dirk Goldgar said:
Fred Boer said:
Hello, Dirk!
Does the subform try to open anything in Design View? That won't
work
in an MDE, of course.
No...

Is there code behind the subform?
No...

Is there anything "special" about the subform?
Click to expand...

Well, I don't *think* so.. There is only 1 control, a textbox. I will
append at the end of this message the two queries involved in the
subform...
If you delete the subform and the code that references it, can you
make an
Click to expand...
MDE that runs without the error?

Yes... That's why I think it is the subform, and I strongly suspect
that the problem is with the queries, but since everything seems to
work ok as an MDB, I can't tell what is wrong with the MDE. I have
tried running the MDE on a number of computers, and I have also
reinstalled the Access Runtime files and tried that too, with no
success.

Thanks for your help!

Fred


Saved Query:

SELECT Lb.Book_ID, Au.AuthorLastName & ", " & Au.AuthorFirstName & "
" & Au.AuthorMiddleName AS Author, Lb.Title, Lb.CopyNumber,
Lb.NumberOfVolumes, Lb.VolumeNumber, Lb.Dewey, Lo.Location,
BA.PrimaryAuthor
FROM Tbl_Location AS Lo INNER JOIN (Tbl_Library AS Lb INNER JOIN
(Tbl_Author AS Au INNER JOIN Tbl_BookAuthor AS BA ON Au.Author_ID =
BA.Author_ID) ON Lb.Book_ID = BA.Book_ID) ON Lo.Location_ID =
Lb.Location_ID
WHERE (((BA.PrimaryAuthor)=-1));

Recordsource of Subform:

SELECT Qry_LabelSpine.Book_ID,
UCase(Left([Qry_LabelSpine].[Author],3)) AS Cutter
FROM Qry_LabelSpine
WHERE (((Qry_LabelSpine.PrimaryAuthor)=-1));
Click to expand...

Hmm I don't see anything wrong with those offhand. If you select those
query results into tables and use the tables in place of the queries,
does it make a difference?

Does the main form do anything with the properties of the subform
control, such as change the Source Object or the Link Master/Child
Fields properties?

Does the MDE fail no matter where you run it? Have you verified that
there are no broken references?

I have to go out now for the evening. If you're still stuck, see if you
can make a cut-down, minimal version of the database that has the same
problem, then compact it, zip it, and send it to me.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)
Click to expand...
 
Fred Boer said:
Ok, well I have it fixed... As you suspected, Dirk, it was a
references problem. I *had* been careful to check the references when
developing the form, which I do in the default Access 2000 file
format. These were always correct. What I *didn't* do, was check them
after conversion to the Access 2002 file format (before creating the
MDE). The conversion process was adding a new reference.

A2K:

Visual Basic for Applications
Microsoft Access 10.0 Object Library
Microsoft DAO 3.6 Object Library

A2K2

Visual Basic for Applications
Microsoft Access 10.0 Object Library
Microsoft DAO 3.6 Object Library
Microsoft Office XP Web Components

Removing this last reference solved the problem. So it was my fault,
but it just didn't occur to me that references would be changed on
conversion...
Click to expand...

Interesting. I suppose I'm not completely surprised that it would be
adding that reference, but I am surprised that it would be broken as
added.
 
Back
Top