Missing reference SSAPI.DLL

[Phil Chenoweth]

I loaded Office 2003, including Access, onto a new ACER laptop running XP
Media and did the online updates. I copied an existing .MDB (say X.MDB),
which had previously been running under XP Home, onto the new computer. On
starting it, a message "missing/broken reference to SSAPI.DLL" displayed.
Then the editor displayed the problem in the code as the word 'Date' (today's
date) but Tools > References was greyed out. So I created a new .MDB, entered
the editor and set all the references (about 19) that I had been using for
X.MDB on the previous computer. (There is no Reference in Access called
"SSAPI.DLL".) I then re-started X.MDB on the new computer with the same
result as described above.
I would be very grateful for any help with this problem?

 

[Douglas J. Steele]

I'm not quite sure I follow what you did. You created a new MDB and set all
of the references. Did you then import everything from the old database into
that new database and try to use the new database, or did you strictly shut
down the new database, and then try to use the old database again? It's the
former you needed to do.

When you tried to get the references in the original database but Tools |
References was greyed out, was the database in Debug mode? Go to the Debug
menu and select End if it's enabled.

 

[Guest]

What are you doing with 19 references! Possibly some design
changes might be in order.

SSAPI is normally a Source Safe dll, but it could be anything.
Are you using VSS automation? What references are you
using?

(david)