dbOpenDynaset nx() and other throw errors and won't compile

[MikeVuckovic]

I inherited an Access database that occasionally will get corrupted on the network.


Up until now the compact and repair function has resolved any issues.
But a few days ago users are reporting error message of Nx() Variable not defined.
When I try to compile the database it throws an error Variable not defined.

Not sure where to go from here.
Checked references for anything missing, there are none.
Access 2013 running on Windows 10 64 bit / Windows 7 32 and 64 bit machines.

Thanks in advance

[ranman256]

why use dbOpenDynaset ?

just open the query:
docmd.openquery "qsMyquery"

[Micron]

You may have to open a new db, save it, then import all objects into it. Then I'd check to see if
a) OPTION EXPLICIT is at the top of every code module, and if not, add it. Google it if you are unfamiliar. I'd also set the vb editor option to "require variable declaration"
b) keep compiling until you find and fix every non-declared variable and/or add every project reference (library) that may be missing

I think your problem is a lot bigger than how you call a query, or don't.

[MikeVuckovic]

That's not the issue.
This is a production database that has been around for 6 + years.
This issue just started, for no apparent reason.
Trying to figure out how the reserved functions and word for Access just error or won't compile?
When running a report the Nx() function uses everywhere throughout the database throws and error, like Access doesn't know what that function is.

[ssanfu]

But then again, it could be the issue.... you just don't know.
EVERY one of my dBs has these two lines at the top of every module

Option Compare Database
Option Explicit

It sounds like you have incremental corruption. I am curious.... is the db split? And each used has a COPY of the FE on their local computer?