J
jsyeldezian
Hi all,
I have a "large" (1GB) multi-user database that all of the sudden
starting throwing the "invalid use of null error" for EVERY query in
the database when opened straight into design view. This db has been
working fine for months until today.
So far, I've compacted and repaired, confirmed that all fields passed
into functions are not null, and checked that all VBA references are
intact. Nothing worked.
When creating a new query and executing from design view all single
source queries run fine (if you save then go back into design view you
get the error). However, for multi-source queries with linked tables
the error will occur at run time (and as with the others, when you try
to open in design view after saving).
Any thoughts? What does Access "check" or do when you open a query in
design view? If this were VBA, I'd immediately say it was a compile
time error, it happens that fast after opening in design view.
Thanks!
I have a "large" (1GB) multi-user database that all of the sudden
starting throwing the "invalid use of null error" for EVERY query in
the database when opened straight into design view. This db has been
working fine for months until today.
So far, I've compacted and repaired, confirmed that all fields passed
into functions are not null, and checked that all VBA references are
intact. Nothing worked.
When creating a new query and executing from design view all single
source queries run fine (if you save then go back into design view you
get the error). However, for multi-source queries with linked tables
the error will occur at run time (and as with the others, when you try
to open in design view after saving).
Any thoughts? What does Access "check" or do when you open a query in
design view? If this were VBA, I'd immediately say it was a compile
time error, it happens that fast after opening in design view.
Thanks!