Hi friendly people ![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
I am running Access 2003 and office 2000 on an XP install and am encountering the following errors..
"Security warning: Unsafe expressions are not blocked" which prompted me to install new MS updates - which I did. NO use. I still get the error when I open any Access DB
If I bypass that error I get another error "The file may not be safe if it contains code that was intended to harm your computer..."
In vain I tried to isolate the problem and import the tables and queries I desperately need into a new blank Access DB ...
In doing this I got two errors - 1 - Disk or network error and 2 - Invalid database object reference -- in that order.
This whole problem began when I was unable to run any typw of date parameter other than a [pBegindate] to [penddate] function.
At that point my IT people took over and reinstalled Access and office upgrading it to its current non-functional configuration.
I have a feeling this is a missing reference but have no code in any front end DB to test that theory on...any ideas..
BTW - if I cannot fix this I cannot work which means I cannot make any money today --I will make a donation to the Access gods in the honor of the person who helps me resolve this!
Thanks much!
K![Stick out tongue :p :p](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
I am running Access 2003 and office 2000 on an XP install and am encountering the following errors..
"Security warning: Unsafe expressions are not blocked" which prompted me to install new MS updates - which I did. NO use. I still get the error when I open any Access DB
If I bypass that error I get another error "The file may not be safe if it contains code that was intended to harm your computer..."
In vain I tried to isolate the problem and import the tables and queries I desperately need into a new blank Access DB ...
In doing this I got two errors - 1 - Disk or network error and 2 - Invalid database object reference -- in that order.
This whole problem began when I was unable to run any typw of date parameter other than a [pBegindate] to [penddate] function.
At that point my IT people took over and reinstalled Access and office upgrading it to its current non-functional configuration.
I have a feeling this is a missing reference but have no code in any front end DB to test that theory on...any ideas..
BTW - if I cannot fix this I cannot work which means I cannot make any money today --I will make a donation to the Access gods in the honor of the person who helps me resolve this!
Thanks much!
K