01-13-2021, 05:39 AM
Mike:
There is a problem with that idea. The only way for me to get the file to you is to export it from my database as a PDF as I completely modified the original problem file.
What is weird is, I did that PDF export and decided to try and re-import the local MSP exported PDF file back into my database to see if the black screen problem would repeat itself...
...it doesn't.
I also tried importing a smaller PDF file into my database with links & bookmarks via the Companion to see if the problem was related to Acrobat created links or bookmarks and that file exhibits NO black screen when opening.
Therefore, I have a funny feeling the original PDF I imported into MS via the Companion, got corrupted in the transfer process (probably because I got impatient and tried to look at it in the Companion before it finished transferring). It wouldn't be the first time a file I transferred via the Companion got screwed up in the transfer process. In all of those other cases, I just deleted the problem file from my database, re-imported it and all was well.
As an experiment, I tried a transfer of another similarly large (16 MB) PDF file via the Companion and it it also exhibited some weird behavior. I waited until I saw that it had successfully transferred to my database in the "Connection to PC Status Log" but it wouldn't disconnect from the Companion when I clicked DISCONNECT. I don't know if that meant it was still transferring despite what the Status Log read, but I had to close the Companion to get it to disconnect.
When I tried to open it the first time, I got a black screen.
So again I exported the newly transferred file as a PDF via MSP on to the machine running MSP. I deleted the file from my database and re-imported the exported local file back into my database.
When I opened it, just like my earlier experiment, NO black screen.
This leads this totally uninitiated person to conclude it has something to do with the transfer of large files via the Companion either because they are not finished transferring despite giving that indication on the Status Log and as a result the file is getting corrupted.
I tested THAT theory by directly importing the same large file locally via a USB stick in to my database on the machine hosting MSP. When I imported it that way, it opened perfectly.
I hope this helps.
There is a problem with that idea. The only way for me to get the file to you is to export it from my database as a PDF as I completely modified the original problem file.
What is weird is, I did that PDF export and decided to try and re-import the local MSP exported PDF file back into my database to see if the black screen problem would repeat itself...
...it doesn't.
I also tried importing a smaller PDF file into my database with links & bookmarks via the Companion to see if the problem was related to Acrobat created links or bookmarks and that file exhibits NO black screen when opening.
Therefore, I have a funny feeling the original PDF I imported into MS via the Companion, got corrupted in the transfer process (probably because I got impatient and tried to look at it in the Companion before it finished transferring). It wouldn't be the first time a file I transferred via the Companion got screwed up in the transfer process. In all of those other cases, I just deleted the problem file from my database, re-imported it and all was well.
As an experiment, I tried a transfer of another similarly large (16 MB) PDF file via the Companion and it it also exhibited some weird behavior. I waited until I saw that it had successfully transferred to my database in the "Connection to PC Status Log" but it wouldn't disconnect from the Companion when I clicked DISCONNECT. I don't know if that meant it was still transferring despite what the Status Log read, but I had to close the Companion to get it to disconnect.
When I tried to open it the first time, I got a black screen.
So again I exported the newly transferred file as a PDF via MSP on to the machine running MSP. I deleted the file from my database and re-imported the exported local file back into my database.
When I opened it, just like my earlier experiment, NO black screen.
This leads this totally uninitiated person to conclude it has something to do with the transfer of large files via the Companion either because they are not finished transferring despite giving that indication on the Status Log and as a result the file is getting corrupted.
I tested THAT theory by directly importing the same large file locally via a USB stick in to my database on the machine hosting MSP. When I imported it that way, it opened perfectly.
I hope this helps.