Hi - I get an dialog box showing "Unsepecified error" every time I try to add a PDF attachment to a reference. But the attachment is still added nevertheless - it's just an annoyance.
I don't know if it is related or a separate problem but when attempting to rebuild the database using the rebuild.exe tool (ie with Biblioscape closed), I receive another error message "DBISAM Engine error #11013 Access denied to table 'C\...borrower.DAT".
I frequently get these "access denied" errors for various database tables that often mysteriously fix themselves with a reboot. Unfortunately a reboot didn't fix this one nor did a complete resintallation of Biblioscape, so I figure there is something wrong with my own database.
BTW I am using V8.04.
When you try to rebuild a
When you try to rebuild a database, the problem needs exclusive access to the database. If you have BiblioWeb running or another user opening the database, you will get the access error.
I can understand that and
I can understand that and that's why this single user database was closed when I ran the rebuild utility. But I am also bothered by the PDF error that keeps popping up every time I try to attach a new PDF file. Further investigation shows that I get the same error when trying to open PDFs from the PDF tab for the reference and they won't open at all. I have both Adobe Reader 9 and Adobe Acrobat 9 Pro installed and have never has this problem before.
I'd appreciate some help with this as I frequently use the PDF panel.
Biblioscape uses Acrobat
Biblioscape uses Acrobat Reader to display the PDF file. The error messages suggests there is a problem with the Acrobat Reader ActiveX controll. People with Acrobat Pro installed have reported problems before. I suggest you reinstall Acrobat Reader.
Okay - so I uninstalled
Okay - so I uninstalled Adobe reader and reinstalled the latest version and guess what? The problem is still there. Is it worth packing my database and sending it to you?
There is no need to send
There is no need to send your database. This problem has been reported before when Acrobat Pro is installed on the same machine. Some users reported reinstall Reader has solved their problem. It seems Acrobat Pro changed something in the Reader ActiveX control which is used by Biblioscape.