I have an Access Data Project that is returning the following error msg for one user only: 'run-time error 430' "Class does not
support automation or does not support expected
interface. "
  When I press debug, it takes me to the following line of
code:
"set conn = currentproject.connection"

  It looks like some sort of issue with
currentproject.connection, but I'm not sure what it could
be. Again, Only one user is having this problem. They
can open the forms without a problem, but none of the
combo boxes are populated.

The user may have a different version of MDAC than the rest.

This error may occur when software attempts to access a database file by referencing libraries that are a different version than those installed on the computer. Update the MDAC to version consisting with your application and make sure all references to the DLL are registered.

I do not think that you can use currentproject.connection in an ADP. Use an ADO connection instead.



Sal

Just as a point of clarification, CurrentProject.Connection is fine in ADPs too. For example, the following dumps the contents of the Customers table to the debug window in both the Northwind and the NorthwindCS DBs.

Sub Main()
    Dim cnn As ADODB.Connection
    Dim rst As ADODB.Recordset
    Dim strSQL As String

    Set cnn = CurrentProject.Connection

    strSQL = "SELECT * FROM Customers"

    Set rst = New ADODB.Recordset
    rst.Open strSQL, cnn

   ' Print the values for the fields in
   ' the recordset in the debug window
    Debug.Print rst.GetString(adClipString, , ";")

End Sub


Bob

There's no problem with using currentproject.connection in an ADP.


Brian Skelton
Braxis Computer Services Ltd.

Thanks for all the help. I think the MDAC issus is probably the most likely. Unfortunately, I haven't been able to get the user to update yet, so I don't know for sure. I did find the MS Knowledge Base article below.

http://support.microsoft.com/default...;en-us;Q248404

I stand corrected. Thank you Bob. By the way, welcome back to the forum.



Sal

Thanks Sal. Glad to see the Access/Access VBA forums are still alive and well. I've been off in .NET land, but just installed Access 2003 and figured it would be a good time to try and remember all the Access stuff I forgot.

Bob