Hi Paul,
I was trying to do a major reorganization of my category structure today and in the process of trying to move a large number of records to a new category I seemed to have stumbled on some kind of corruption. This is the error message: "DBISAM Engine Error # 11949 SQL error - Unknown or unexpected symbol " found in Where clause." I have tried rebuilding the database twice and each time it finds no corruption. The problem seems to be associated with one or a few records that are relatively old. Biblioscape seems to work fine until I try to click on one of these records and then it goes into a cycles of error messages. I would happily delete the records, but it won't allow me to do that. Any ideas?
Thanks.
Matt
Hi Paul I'm getting this,
Hi Paul
I'm getting this, too. In my case it seems to be when I'm opening references from a list that comes from a fast search. It doesn't seem to do it when I'm opening references from a normal folder. I've rebuilt the database -- no change.
Also, when I click on Advanced Search, the calendars appear very slowly, taking several seconds to display. This seems new behaviour.
I'm using Build 26.
Hugh
1. Please get the 7.26
1. Please get the 7.26 patch again. There is a bug introduced in initial 7.26 release, it is now fixed. Please let me know the result.
2. Please go to "Tools | Options" window "Database" tab, add "Date created" and "Date modified" as sedondary index. Then the display will be very fast. Those two sec indexes will be added automatically in 7.3 release. Thanks.
Thanks, Paul. Note 2 solves
Thanks, Paul. Note 2 solves the date display problem. However, the first problem -- the DBISAM Engine Error -- is still there even though I've downloaded the newest version of the 7.26 patch. I'm afraid it's beginning to be a real nuisance: it's constantly getting in the way of being able to use Biblioscape now.
Hugh
I cannot reproduce this.
I cannot reproduce this. Please let me know a more detailed step by step instruction to reproduce it. Thanks.
I can't reproduce this
I can't reproduce this either now -- perhaps it's been fixed in the 7.27 patch. I'll let you know if it reappears.
Two suggestions for the Advanced Search:
1. Even with the changes you suggest, it still takes a noticeable time for the calendars below the Advanced Search conditions to display on a BiblioRemote link, especially if the Internet connection isn't a fast one. How about an option to suppress them?
2. Could a checkbox be added to Advanced Search to allow the user to select case-sensitive or case-insensitive searches? For a lot of the time case-insensitive searches are safer, given that one can never be sure how consistently references have been entered (e.g. sometimes, when references are downloaded, author names etc . are in upper case, and sometimes they're not), but there may be times when case-sensitive is important.
Has this forum stopped notifying the user by e-mail when a reply has been posted to a thread they're watching? I don't seem to be getting these e-mails now.
Paul It's started again,
Paul
It's started again, and I can reproduce it, so I'll send you the database with a step-by-step set of instructions to get the problem.
Possible cure for the DBISAM problem?
Two of my machines had this problem, but then I found that a third one didn't. So I removed Biblioscape from the machines that had this problem and did a clean reinstall on each, and the problem seems to have disappeared (at least, the test that produced it reproducibly no longer does). Next, I copied one of the troublesome installations over to the third computer and ran it there, and indeed it misbehaved on that machine just as it had in its previous home.
Hugh, Thank you for sending
Hugh, Thank you for sending me the database. I found out the problem is caused by ophaned references. In earlier versions of Biblioscape, references don't have to be in any folder. This is no longer allowed in versioni 7. But the upgrade routine didn't check this during conversion. So there are still orphaned references in your database. When working on those references, the problem occured. In version 7.3 release, Biblioscape will check all orphaned references and put them into a references folder called "Orphaned". Thanks.
I just hit the problem
I just hit the problem again, on an installation that I'd refreshed as described above (i.e. by doing a clean reinstall of Biblioscape). Then I found that the reference in question was one of the orphaned references -- it wasn't in any folders. When I moved it to a folder, the problem went away.
Version 7.3 will check
Version 7.3 will check ophaned references and put them into the "Ophaned" folder. Do you mean there is an ophaned reference in the sample database with Biblioscape installation? Which record is it? Thanks.
No, it isn't the sample
No, it isn't the sample database -- it's my own database, which seems to have quite a number of orphaned references, as you found when you checked it.
It'll be very helpful to have 7.3 checking for orphaned references -- am I correct in assuming that it will be checking existing Biblioscape 7 databases?
It will check existing
It will check existing database when it is first converted to version 7.3 format.
I see -- so the 7.3 database
I see -- so the 7.3 database format will be a little different from the 7.2 format, will it?
There are some database
There are some database schema changes. Version 7.3 will include the beta release of the new composition module for writing books and theses.
1. In the next patch
1. In the next patch release, the date highlight feature will be automatically turned off when connecting to BiblioRemote. 2. Advanced search is case sensitive by default. The Fast Search is always case insensitive. The email notifying feature is turned off. We will add it back in the future. Thanks.
Hi Paul, I downloaded the
Hi Paul, I downloaded the new patch, but the problem remains. When I select a large group of references and attempt to categorize them I produce the SQL error. It appears that it only happens, however, with a group of references that includes some of my oldest references, I have no problem with a large list of my more recently created references. I have a feeling that there is something wonky with some of these older references, but the repair database does not identify the problem. These may be references that I imported from endnote when I first started using BS. This is not a debilitating bug for me, the program otherwise is working fine, but I thought you'd like to know that something remains amiss.
matt
Matt, please zip all the
Matt, please zip all the files under your database folder and email me the zip. Then let me know how to reproduce it in detail. Thanks.
That seemed to do the trick.
That seemed to do the trick. Thanks Paul.
matt
Actually, the problem
Actually, the problem remains. It only happens now when I try to change the category status of a large group of references, and I think it only happens when that task involves my older references, at least that's how it appears. This is not a debilitating issue, but there does seem to be some sort of ongoing bug.
matt