CurrentProject Compile error (Access 2002, SP-2)

[jbrain]

My application FE, which has worked great without problems is suddenly giving an error "Object library Feature not supported" whenever anyone clicks on a button on the switchboard. My system is down until I can figure out what is happening. The code it jumps to is "Set conCurr = CurrentProject.Connection". I didn't write any of the code, have no idea what it's really doing, but need to get system back up and running.
Any ideas would greatly be appreciated.
Thank you,
John Brain

[HansV]

Open the database (with the Shift key down to bypass the startup options)
Activate the Visual Basic Editor (Alt+F11)
Select Tools | References...
Which references are checked, and in which order?

[jbrain]

Thank you Hans.
Visual Basic For Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft ActiveX data Objects 2.5 Library
Microsoft Office XP Web Components
Microsoft DAO 3.6 object Library

Also, I've observed the following. I can load and run the version that sits completely on my hard drive (development copy). If I remote access into the Server, I can load and run the system too. When I use my FE from local drive to BE on Server I run into problems. No known updates were made over weekend, but someone did remote log in with laptop (but they had no problems)
Thank you for helping with this.
John Brain

[jbrain]

Hans,
It seems to be working now but I don't know why. I noticed the Terminal Server had Microsoft ActiveX data Objects 2.7 Library loaded. I went back to my computer, unchecked 2.5 and checked 2.7. Recompiled and it all worked fine. I put the new version out to be updated automaticaly with Tony's utility, and now when I check References, it still shows 2.5 being loaded. But, the system is working and people can get into it. If you have any idea what it is I'd be really really interested.
Thank you again for your help.
John Brain,
Technology Director
UCP of Central Arizona

[HansV]

Have you tried Tools | References... in the situation where the FE is local and the BE is on the server?

I see that you have references to both ADO (ActiveX Data Objects) and DAO. Assuming that there is a declaration for conCurr:

Dim conCurr As Connection
or
Dim conCurr As Object

change it to

Dim conCurr As ADODB.Connection

If there is no such declaration, add it.

[WendellB]

<hr>I put the new version out to be updated automaticaly with Tony's utility<hr>

Just curious what that is and where it can be found.

[HansV]

I was posting my reply <post#=358203>post 358203</post#> while you reported the problem solved. I think the ADO 2.5 / 2.7 difference was probably the culprit, so I wouldn't pursue my suggestions.

[jbrain]

<P ID="edit" class=small>(Edited by WendellB on 29-Mar-04 12:24. Activate Link to Tony Toews website (see Help 19))</P>A utility developed by Tony Toews (I believe that's his last name) with Granite Consulting. In short, it updates the FE on local machines by comparing it to a "Current Version" on the server. If an update was made, it automatically copies the new FE to the local computer. It does a few other things too, but has saved me tons of time updating everyone's FE. Check it out at: http://www.granite.ab.ca/access/autofe.htm

Hans, I will do those things you recommended, but now that system is up I've moved onto a major security issue at work (physical Security system, not Access DB security).

I'll get back to you with updates later today.
Thanks again,
John Brain