Don't think so. Its a vba program in word 2007.
True, the VBA code is running in Word, but the error, 3343 is an
Access (or at least a DB) Runtime error that means: "Unrecognized
database format."
It could mean that the DB is corrupt. In which case he might have to
try to copy to a new, blank DB....or use a backup.
However, assuming he's using ADO to connect to the DB via Word, it may
be that the Provider isn't recognizing the new format. I haven't yet
been brave enough to convert any of my Word -- DB ADO projects over
to 2007 DBs, so I haven't been hit with this problem YET. But it may
mean that you need to use a new Provider, versus the one for JET.
But as I said, the Access MVPs may have better info about the 2007
format, as I've been chicken to work with it much yet. And since few
Word users take advantage of ADO DB connectivity, even the Word VBA
group would be better than this new users group, where most Qs are
basic and this is an advanced one.
Here's the connection string for Access 2007. So if this is what the
user has already coded...then my guess is a corrupt DB. Try repairing
or copying to a new DB. Although ya might first want to make a mini
bogus one in 2007 to see if the connection works at all!
http://www.connectionstrings.com/?carrier=access2007
Good luck!
Dian D. Chapman
Technical Consultant, Microsoft MVP
MOS Certified Instructor, Editor/TechTrax Ezine
https://mvp.support.microsoft.com/profile/Dian.Chapman
Free PC Tutorials:
http://www.mousetrax.com/techtrax
Free Word Tricks eBook:
http://www.mousetrax.com/books.html
Optimize your business docs:
http://www.mousetrax.com/consulting
Learn VBA the easy way:
http://www.mousetrax.com/techcourses.html