Typically clicking Yes in the SQL dialog box should disconnect the old data source, but I would at least "make sure" by e.g. The problem, but in fact Word "reverts" to the previous source the next time you open. If you proceed from the dialog I mention, then choose the option to find the data source in the next or subsequent dialog, it does then appear that you have corrected That will happen if the previous data source has not been properly disconnected - e.g. If no, the wrong data source is "sticking". Does that file exist? Is it the one you expect? If yes, again, I would suspect the Excel file. When you see the SQL warning and click Yes, do you then see a dialog box which provides the workbook path/name. For the default OLE DB connection type, the SQL message is the correct one - the SQL does not reference the workbook path or name - that comes from the file name or connection string which is not displayed in that dialog box.ģ. That may show that the file is/was at fault.Ģ. Do you have the same problem if you try to connect a completely new Word document to the data source? If so, probably something wrong with the Excel file - if you can reconstruct it, or even create a test file with the same sheet name and column names,
There is also a Power Automate option for converting Excel to PDF which means you can create automated processes that convert your files to PDF.1. Luckily it’s pretty easy and there are a few options available.
This means you can convert PDF files as part of some automated process. There is a Power Automate action that can convert files to PDF. Convert File to PDF in Power AutomateĪll the previous options to convert your Excel file to PDF are great and they will save you valuable clicks, but they are not automated. The PDF of the converted Excel file will also be added as an attachment. When you press this command, it will automatically create a new Outlook email with a subject line of the Excel workbook name.