3075-Function Not Available

[hughesai]

Hi all,

I am getting the above error message on a number of PCs when running queries. Everything works fine on my PC and many more, but occurs on a number of users PCs. The functions which are not recognised are usually LEFT(), RIGHT(), FORMAT(), DATE() etc.

I know this is a problem with references, and different versions etc as described in a number of threads here, FAQ181-936, and the microsoft document at

http://support.microsoft.com/support/kb/articles/Q194/3/74.ASP.

I have incorporated the MS code in this article to fix broken references on launch of my database. When monitoring this I can tell that the code is being invoked, references alledgedly being fixed up, and code recompiled, but I still get the error ! ?

I can't be sure that all the references are correct because the problem is only occuring on PCs with run-time licenses.

This piece of code has worked for me in the past, but doen't seem to be effective this time.

I have also found all the referenced files on my PC and checked on the other PCs that they are there. I found all to be present, some in differnt places. To be sure this was not causing the problem, I copied them to the "correct" place per my PC's setup - I still got the same error.

Can anybody suggest why this is happening and/or how to correct it?

Aidan Hughes.

 

[hughesai]

Sorry - should have also mentioned - I'm running Access 97 on Windows 2000 PCs !

 

[psemianonymous]

I had this problem when I used the "Startup" options of the database to open a form. Remove that, and put the "OpenForm" in your autoexec macro, and the problem disappears. It's odd, but it works. Apparently "Startup" runs a lot earlier in the bootup process, when Access is apparently still loading libraries and such.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[psemianonymous]

I would also like to add that it randomly started happening--I have never found the cause for this error.

 

[hughesai]

Thanks foolio12.

Your suggestion did not work, but got me thinking that it was a timing issue.

I have a routine which prevents the main switchboard from closing which means that the application must be exited by pressing the exit button rather than just closing Access (the exit button writes information to a log file !)

Anyway, I was running the reference check after this routine. It seems that the save and compile was failing because the main switchboard could not be closed, and the references were not updated.

I changed the order of the routines, and lo and behold, everythng updated correctly, and I am no longer getting my errors.

Best Regards and thanks for your help,

Aidan Hughes