Many forms have strange errors: You entered an expression that has an invalid reference to the prope

[josh]

Hello,

I have inherited an Access app that was originally build on Access 2.0,
upgraded to Access 95 (I think) and now resides in Access 97. I say
originated in 2.0 because many DoCmd commands have 2.0 constants
specified as parameters.

If I put a break point in the Form_Open event of my main form and then
open up the debugger, I see numerous objects/properties with the
following error messages:

===========================================

: acHiddenCurrentPage : <You entered an expression that has an invalid
reference to the property acHiddenCurrentPage.@The property may not
exist or may not apply to the object you specified.@@2@2

: ConnectControl : <You entered an expression that has an invalid
reference to the property ConnectControl.@The property may not exist or
may not apply to the object you specified.@@2@2015567@1>

: LogicalPageHeight : <You entered an expression that has an invalid
reference to the property LogicalPageHeight.@The property may not exist
or may not apply to the object you specified.@@2@20155

: Parent : <The expression you entered has an invalid reference to the
Parent property.@For example, you may be using the Parent property with
a control on a main form or report rather than with

: acHiddenCurrentPage : <You entered an expression that has an invalid
reference to the property acHiddenCurrentPage.@The property may not
exist or may not apply to the object you specified.@@2@2

===========================================

I searchd the nes groups and saw many refrences to similar issues. One
postng recommended loading the db from the command line using
/decompile switch, then opening it back up, opening a code module and
recompiling. I tried this but I still see these errors.

Another issue I have with this database...

If I run the app not in degug mode, it breaks on a particular line of
code (which happens to be setting a string variable to some specific
text.

I have no break points defined and and not running this db in debug
mode.

Any ideas on what would cause the form to break into debug mode? This
module does have a standard error handler defined but it doesn't appear
to be hitting the error handler.

Thanks for your time and recommendations.

Josh Blair
Evergreen, CO

 

[Alex Dybenko]

Hi,
when you convert from Access 2.0 - a DAO 2.5/3.5 compatibility layer
library is added to your project. perhaps it is missing now and cause these
errors. check project references and remove this one. also check that all
other references are in place

 

[joshblair]

Alex,

Thanks for the recommendation. The DAO 2.5/3.5 comp. layer was still
refrenced instead of DAO 3.51. I removed the reference to DAO 2.5/3.5
and added DAO 3.51, then changed all the syntax from rs.fieldname to
rs!fieldname and recompiled.

If I put a break point in the Form_Open event in my main form and then
open the debugger and expand the Me object container, the
acHiddenCurrentPage property has the following error message listed:

: acHiddenCurrentPage : <You entered an expression that has an invalid
reference to the property acHiddenCurrentPage.@The property may not
exist or may not apply to the object you specified.@@2@2

There are many others like this in different properties/objects in the
debugger. Any ideas?

Thanks,

Josh Blair
Evergreen, CO

 

[Alex Dybenko]

Hi Josh,
I have the same. But what do you want to get with this property?
it just state that property in not available currently

 

[joshblair]

Alex, are you saying that these errors that I see in the debugger (not
at runtime) are not a problem? If so that is great. I was under the
impression that this Acess DB that I inherited had been upgraded from
Access 2.0 to Access 95 to Access 97 had some baggage that was causing
these issues.

At any rate, thanks for the tip on upgradign the DAO references.

Take Care, and thanks for your time and information,

Josh Blair
Evergreen, CO

 

[Alex Dybenko]

Hi,
yes, this is what I think. You can create new database, add a from there
and check that property - you will get the same result

 

[joshblair]

Thanks Alex. I appreciate your time and insight.

Take Care,

Josh Blair
Evergreen, CO