Issue with Report no longer printing due to Windows Update

What is different between the programs?

Do they connect to the same database?
DO they call the reports in the same way?

Were these running under Windows 7 before?

What version of Crystal are you using?

mlmcc

What is different between the programs?  The programs are similar but serve different areas of an analytical laboratory.

Do they connect to the same database?  No.  Once again similar but there are a number of different fields
DO they call the reports in the same way?  Yes the same.

Were these running under Windows 7 before?  Yes, for several years until the recent Windows Update.

What version of Crystal are you using? 8.5

I have seen questions like this before on this site and similar discussion on the SAP site.  I don't recall if there was a definitive answer.

It seems some applications and reports work under Windows 7 and others have issues.

Have you tried recompiling the application with the updates in place?

Have you rebuilt the ODBC connections?

Do you have Crystal installed on one of the machines with the updates?
If so have you tried opening the reports, refreshing the data, then saving the report?

I will look for the discussions on here and SAP to see if there are other ideas.

mlmcc

I've narrowed it down to the actual Windows Update KB4480970.  When I remove the update the reports work again.   When I let Windows Update for KB4480970 the reports stop working.  

I read up on the KB4480970 and am focusing on the Access Database portion of the update.  I'll let you know what I find.  Probably will be late afternoon PST before I get to it.

Thanks mlmcc, appreciate your input!

Is the database in question on a network share?

https://borncity.com/win/2019/01/12/fix-for-the-windows-7-smb-network-bug-caused-by-update-kb4480970-kb4480960/

mlmcc

It is on a network share but a similar system with the same Crystal Reports is printing fine.  I was hoping to get into it again yesterday but got delayed to today.  

Thanks for the suggestion mlmcc.  I'll try your suggestion once I take a look at the databases.

Make sure you didn't lose access to the share.

Maybe change the connection to use the fully qualified path rather than through the share.  I had to do that with one of the programs I wrote since not all the users had the shared mapped the same way

Switch the report away from using DAO connectivity to Excel/Access.

The recent Windows Update KB4480970 causes reporting tools such as Crystal Reports to not operate if any Access Database field names are above 30 characters.  This was the case with one field in the Report Headers Table.  Therefore, any report containing report headers would have an issue reviewing or printing.  I truncated the field name in the table and all the reports started working again.  Thanks mlmcc and Ido for your input.  Ido, your solution probably would have worked as well.