These are all files created from a Word doc (a very old one) embedded in the app. We're going to try replace that doc....

Hi Shawn;

It could be (my theory) that depending on where the user is on a network segment (latency) & the size of the document Blob, the odd user gets timed out.

I would suggest adding a TRY..CATCH around your OLE code and if it fails, do a yield / sleep command or two - then retry.

If the retry fails, alert the app user to the error. Maybe even log the details around the failure from the Exception 0bject's Code & Error Text for further analysis. HTH

Regards ... Chris

This could be the problem. The SQL Server is accessed across the internet. But this app has been running for years as is and this issue started to pop-up just a few months ago. I feel like a security setting from Defender or some other avenue is interfering with the OLE activity. I don't feel that this issue is necessarily one that should be solved in this forum as I doubt it's actually a coding issue. Was just hoping someone might have seen this happening to them lately. Thanks.

PS: The other thing I encountered a few times in my various PB developer days was a crashing issue on a few App user's machines. When we went to check the Blob data on a few rows, we found that the Blob data stream was not saved properly. So when the SelectBlob was executed behind the scenes and the OLE control tried to paint the control's area, it crashed and took the PB App with it. We finally tracked down a few DB Rows that had this corrupt blob issue. The reason why only a few App users had this issue was that they were trying to update a customer record that only that they were responsible for. Hence the crashing for specific users when those few customer's records were being accessed. We finally traced the problem by logging the Table & Primary Key(s) being used in the App's specific process that crashed. So after the crash, we could then examine the Blog table's column using a DBA tool. That was the Ah-Ha moment when we saw the corrupted Blob data stream. The fix was to update the corrupt Blob column in the odd Table row with the proper (entire) data stream. Turns out that the App that updated these Blobs originally, did not complete the DB update properly.

Hi Shawn;

DOCX should be supported if the OLE mapped class that is being used is ""Microsoft Word Document". You would be restricted to DOC files if the OLE mapped class is "Microsoft Word 97".

Yes, Office 2016 is pretty old now. I am not having issues with this in my Office 365 environment.

Regards ... Chris

They are all actually using M365 Apps for Enterprise but the version shows build 16026.xxxxx so i assumed that was still some derivation of 2016.

I'll test with a new .docx file type, see what happens. Thank you.

I never spent the effort to try to troubleshoot. In the Word UI I get this kind of error message: https://filestore.community.support.microsoft.com/api/images/eaf46c90-8ce9-4226-8fdb-07b3f22f4dc6

That looks to me like there should definitely something to see in the event viewer. Maybe have some of your tech staff have a look at it.

regards.

(or install libre office)

:)