ODBC (Word Merge and Access DB)

%3CLINGO-SUB%20id%3D%22lingo-sub-1816407%22%20slang%3D%22en-US%22%3EODBC%20(Word%20Merge%20and%20Access%20DB)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1816407%22%20slang%3D%22en-US%22%3E%3CP%3E1.%20I%20have%20been%20doing%20mail%20merges%20for%20decades%20using%20MS%20WOrd%20and%20MS%20Acces.%3C%2FP%3E%3CP%3E2.%20Currently%20using%20Office%20365%20products.%3C%2FP%3E%3CP%3E3.%20Last%20successful%20merge%20was%20at%20end%20of%20August%202020%3C%2FP%3E%3CP%3E4.%20No%20attempts%20to%20do%20merges%20until%20mid%20October%202020.%3C%2FP%3E%3CP%3E5.%20I%20receive%20what%20appears%20to%20be%20an%20ODBC%20setup%20manager%20window.%3C%2FP%3E%3CP%3E6.%20I%20do%20not%20recall%20ever%20having%20to%20work%20with%20this%20item.%20(see%20attached%20image)%3C%2FP%3E%3CP%3E7.%20At%20the%20bottom%20of%20the%20manager%20there%20is%20a%20test%20button.%26nbsp%3B%20Clicking%20this%20results%20in%20an%20error%20message.%20(see%20attached%20image)%3C%2FP%3E%3CP%3E8.%20I%20have%20worked%20with%20MS%20support%20in%20both%20Windows%20and%20Office%20without%20success.%26nbsp%3B%20The%20following%20has%20been%20tried%3A%20a)%20Office%20repair%3B%20b)%20uninstall%20and%20reinstall%20of%20Office%3B%20c)%20installation%20of%20Access%20redistributable%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1816407%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1816544%22%20slang%3D%22en-US%22%3ERe%3A%20ODBC%20(Word%20Merge%20and%20Access%20DB)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1816544%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F845205%22%20target%3D%22_blank%22%3E%40Chuckz1947%3C%2FA%3E%26nbsp%3BThe%20second%20image%2C%20with%20the%20connection%20dialog%2C%20appears%20to%20indicate%20that%20one%20or%20more%20files%20have%20been%20relocated%20and%20the%20existing%20connection%20is%20not%20pointing%20to%20the%20new%20location(s).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1816664%22%20slang%3D%22en-US%22%3ERe%3A%20ODBC%20(Word%20Merge%20and%20Access%20DB)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1816664%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126074%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20reply.%3C%2FP%3E%3CP%3EThat%E2%80%99s%20what%20it%20would%20seem%20to%20me%20too%2C%20but%20the%20connection%20string%20as%20it%20reads%20%E2%80%9CDSN%3DMS%20Access%20Database%3BDBQ%3DD%3A%5CDOCUMENTS%20-%20COPY%5CMASTERFRONT%5CMaster_fe.mdb%3BDefaultDir%3DD%3A%5CDOCUMENTS%20-%20COPY%5CMASTERFRONT%3BDriverId%3D25%3BFIL%3DMS%20Access%3BMaxBufferSize%3D2048%3BPageTimeout%3D5%3B%E2%80%9D%2C%20appears%20OK%20to%20me%20for%20the%20parts%20that%20I%20understand.%26nbsp%3B%20What%20I%20mean%20is%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20split%20database%20and%20the%20naming%20and%20the%20path%20is%20correct%20(D%3A%5CDOCUMENTS%20-%20COPY%5CMASTERFRONT%5CMaster_fe.mdb).%26nbsp%3B%20This%20is%20where%20all%20of%20my%20queries%2C%20forms%20and%20reports%20are%20located.%20%E2%80%9CMaster_fe.mdb%E2%80%9D%20is%20the%20name%20of%20my%20front%20end.%3C%2FP%3E%3CP%3EThe%20odc%20files%20are%20at%20D%3A%2Fmy%20data%20sources.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20the%20initial%20catalogue%20to%20use%2C%20the%20path%20is%20correct%20as%20I%20see%20it%20(D%3A%5CDOCUMENTS%20-%20COPY%5CMASTERFRONT%5CMaster_fe.mdb)%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20use%20the%20%E2%80%9Ctest%E2%80%9D%2C%20I%20do%20not%20understand%20why%20it%20says%20%E2%80%9Cdata%20source%20name%20not%20found%E2%80%9D%20and%20no%20default%20driver%20specified.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20wondering%20whether%20I%20should%20incorporate%20the%20following%20somewhere%3A%20D%3A%2Fmy%20data%20sources%2C%20and%20if%20so%20where%2C%20but%20when%20I%20get%20the%20opportunity%20from%20within%20the%20Word%20merge%2C%20to%20%E2%80%9Cfind%E2%80%9D%20the%20data%20source%2C%20it%20does%20in%20fact%20point%20to%20the%20subdirectory%20%E2%80%9Cmy%20data%20sources%E2%80%9D.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWhat%20about%20installing%20a%20fresh%20ODBC%20driver%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

1. I have been doing mail merges for decades using MS WOrd and MS Acces.

2. Currently using Office 365 products.

3. Last successful merge was at end of August 2020

4. No attempts to do merges until mid October 2020.

5. I receive what appears to be an ODBC setup manager window.

6. I do not recall ever having to work with this item. (see attached image)

7. At the bottom of the manager there is a test button.  Clicking this results in an error message. (see attached image)

8. I have worked with MS support in both Windows and Office without success.  The following has been tried: a) Office repair; b) uninstall and reinstall of Office; c) installation of Access redistributable

5 Replies
Highlighted

@Chuckz1947 The second image, with the connection dialog, appears to indicate that one or more files have been relocated and the existing connection is not pointing to the new location(s).

Highlighted

@George Hepworth 

Thank you for your reply.

That’s what it would seem to me too, but the connection string as it reads “DSN=MS Access Database;DBQ=D:\DOCUMENTS - COPY\MASTERFRONT\Master_fe.mdb;DefaultDir=D:\DOCUMENTS - COPY\MASTERFRONT;DriverId=25;FIL=MS Access;MaxBufferSize=2048;PageTimeout=5;”, appears OK to me for the parts that I understand.  What I mean is:

 

I have a split database and the naming and the path is correct (D:\DOCUMENTS - COPY\MASTERFRONT\Master_fe.mdb).  This is where all of my queries, forms and reports are located. “Master_fe.mdb” is the name of my front end.

The odc files are at D:/my data sources.

 

For the initial catalogue to use, the path is correct as I see it (D:\DOCUMENTS - COPY\MASTERFRONT\Master_fe.mdb),

 

When I use the “test”, I do not understand why it says “data source name not found” and no default driver specified.

 

I was wondering whether I should incorporate the following somewhere: D:/my data sources, and if so where, but when I get the opportunity from within the Word merge, to “find” the data source, it does in fact point to the subdirectory “my data sources”.


What about installing a fresh ODBC driver?

Highlighted

@Chuckz1947 

I have done some experimentation:

 

1. I get the error messages (as previously  mentioned) when I attempt to run a merge from any Word document that is associated with an ODC file previously created (and was previously working)

2.  If I instead select a new data source from the Word merge document, and I navigate to the appropriate query, I do not get those error messages, but in trying to run the merge I get this error message:

 

Chuckz1947_0-1603921323981.png

Upon checking, there appears to be no evidence of an ODC file having been created.

 

The most important issue of course is in finding the "fix".  More generally, are ODC issues considered Access issues, Word issues or Windows issues?  

I

Highlighted

@Chuckz1947 

I was fortunate to find a consultant who understood the issue and resolved it quickly. 

Highlighted
Care to share to benefit others who may be facing the same issue.