Left, Mid, Right not recognized anymore

[LawraC]

Hi !

I use access 2000 (french) and runtime access 2000 (english) on XP.
After upgrading workstations with last microsoft security patchs, the use of left, mid or right functions in queries doesn't work anymore.
We know now that the patch acted on MDAC, is it the answer?
I don't know how to make it work.

If you have any idea, it would be great.

LawraC

 

[RuralGuy]

I believe all you need to do is refresh the references. Go into the references and unselect DAO or ADO and close out the db. Go back in and select the one you unselected and compile again and then try it. That should fix it.

 

[LawraC]

Still doesn't work.

I unselected all references I could and re-select.
I select DAO 3.6 (Visual Basic for Applications and Microsoft Access 9.0 can't be unselected).
No problem for creating MDE.
The creation add more references :
-OLE Automation,
-Microsoft Visual Basic for Applications Extensibility 5.3,
-Active Setup Control Library
-Microsoft ActiveX Library
-Microsoft Data Access Components Installed Version
-Microsoft Forms 2.0

I can use MDE on my PC without any problem.

but when using MDE on workstations concerned by microsoft update, I still have this message "Function nonavailable : Left". Idem for Right and Mid functions.
These workstations don't have Access 2000 installed, only Runtime

 

[boblarson]

I've experienced this problem with the Comctl32.ocx file. In the references, click browse and browse to C:\Windows\System32 and select that file and click OK, then close the windows, reopen the database and then create the MDE file - try that. If it still doesn't want to work, you can have the program refresh the references by using the info here
http://support.microsoft.com/kb/194374
This says it is good for A97, but it really will work for A2K too. You just might need to make sure DAO is checked in your references and fully qualify
Dim db As Database, rs As Recordset
to Dim db As DAO.Database, rs As DAO.Recordset
since in Access 2000 the default is to not have DAO checked when a new database is created.

 

[The_Doc_Man]

I believe part of the problem is that XP service pack 2 enforces the requirement that all .DLL files be verified / digitally signed - or something equally as restrictive as that.

When you upgraded the workstations, do you know if the update also upgraded the MS Office products? It is not always done automatically. You have to allow it to do the Office updates. Revisit the update site with one of the machines (if you can) and see if you can get separate updates for MS Office. Particularly since you are using a French Access and an English Windows, there is slightly higher than normal chance for confusion anyway.

 

[RuralGuy]

Hmmm...It still sounds like a reference problem of some sort. Here's Doug Steele's excellent article on the subject.

 

[LawraC]

Ok it works but i do not understand, even with articles (thanks), why the MDE's references have to be refreshed during a night.
I mean, one day it works fine. In the night, the PC with the MDE are upgraded but not my PC. and in the following morning MDE doesn't work anymore on the upgraded PC.
And the only solution is just to refresh references and regenerate the MDE on a PC without any updgrade.
It works, but I don't know why and it means that the operation will have to be done for every following upgrades.
Sometimes I know why I prefer Internet Applications.

Thanks a lot for your help.

Lawra

 

[The_Doc_Man]

Oh, perhaps I understand your question better now that you rephrased it.

References are a REGISTRY entry. Each individual machine has its own registry. For machines with a true domain architecture with roving profiles, each distinct USER might require reference updates, since the user profile is ALSO part of the machine's registry.

However, if an administrator sets up the references from an admin account, they might become fixed for that machine on a longer-term basis. Not sure about that one.