Hi all, I have a really annoying problem with a users workstation. There is a development version of the access database that is distributed to workstations using a .bat file. The database is working perfectly on all workstations other than one.
The particular workstation will not let the user run specific Query's, giving a 3075 Error. I have been across the web and realized that this is a problem with the references. However there are no MISSING references, but if i force access to refresh its references, by checking an un-selected reference, then again removing the reference, the database works perfectly. It works perfectly until the user again runs the .bat and receives the latest version of the DB.
I have un-registered and re-registered the references using Regsvr32.exe but still the problem persists.
I have performed a COMPLETELY fresh install of office but still the problem persists.
Is there a way to force access to refresh its references via VBA on open?
Failing that i will be forced to do a clean install of the machine.
The machine developed this problem within a matter of 30 minutes and has been working perfectly for 2-3 years before hand.
Any help is greatly appreciated. :banghead::banghead::banghead:
Thanks
Alex.
The particular workstation will not let the user run specific Query's, giving a 3075 Error. I have been across the web and realized that this is a problem with the references. However there are no MISSING references, but if i force access to refresh its references, by checking an un-selected reference, then again removing the reference, the database works perfectly. It works perfectly until the user again runs the .bat and receives the latest version of the DB.
I have un-registered and re-registered the references using Regsvr32.exe but still the problem persists.
I have performed a COMPLETELY fresh install of office but still the problem persists.
Is there a way to force access to refresh its references via VBA on open?
Failing that i will be forced to do a clean install of the machine.
The machine developed this problem within a matter of 30 minutes and has been working perfectly for 2-3 years before hand.
Any help is greatly appreciated. :banghead::banghead::banghead:
Thanks
Alex.