DBISAM Engine Error # 11949

[tomos]

Could this be from CH&S ? (not sure where it came from - there were about 5 of them when I minimised all other windows - they had never shown in the foreground...

---------------------------
Error..
---------------------------
DBISAM Engine Error # 11949 SQL parsing error - Expected NULL, Date, Time, or Timestamp expression but instead found '0000-00-00 01:30:54.500 AM' in UPDATE SQL statement at line 1, column 130
---------------------------
OK 
---------------------------

[mouser]

CHS does use dbisam, so it could be CHS -- but it's hard to know without more clues..  Hard to see why it would happen out of the blue.  See if CHS is behaving normally otherwise.  Does it create new clips when you copy new stuff, etc.? Have you been using it successfully in other circumstances?

[tomos]

>Does it create new clips when you copy new stuff, etc.?
YES

>Have you been using it successfully in other circumstances?
YES

I'll keep an eye on it and report anything new

[tomos]

it's definitely CH&S - it shows up as CH&S when I alt+tab

---------------------------
Error..
---------------------------
DBISAM Engine Error # 11949 SQL parsing error - Expected NULL, Date, Time, or Timestamp expression but instead found '0000-00-00 03:22:57.500 AM' in UPDATE SQL statement at line 1, column 130
---------------------------
OK 
---------------------------

noticed the time has changed, otherwise the same
it did seem to happen one day when I trying to paste in a web page
could it possibly be clashing with SQLNotes - wild guess simply cause of the "SQL parsing error" and also cause SQLN has html notes pane

Problem is the error warnings are always behind everything else (& I usually keep a full screen) so I've no idea when they happened

Been having a few problems on occasion with CH&S - ctrl+alt+v brings nothing for quite a few seconds, 10 or more, I've given up at that stage.. & pressed it twice or 3 times first it comes up later unexpectedly

[mouser]

i dont think its clashing with sqlnotes.  it's clearly something in the recording of the timestamp on clips.
if nothing else then maybe i can build some logging functionality that will help us track it down.

let's talk in private message and try to work this out rather than doing it on this thread.

[tomos]

'K

[tomos]

Been using Evernote more lately (& still using SQLNotes) -
I get the error with both so it appears to be somehow HTML related

otherwise CH&S works fine

Just wondering:-
I use system default time of YYYY-MM-DD
and notice 0000-00-00 in the error
---------------------------
Error..
---------------------------
DBISAM Engine Error # 11949 SQL parsing error - Expected NULL, Date, Time, or Timestamp expression but instead found '0000-00-00 09:19:34.485 AM' in UPDATE SQL statement at line 1, column 156
---------------------------
OK   
---------------------------

do you think could that be confusing something somewhere?

[FreddyB]

Just got the same error - DBISAM Engine Error # 11949 SQL parsing error - Expected exression but instead found ) in DELETE SQL statement at line 1, column 30.

This occurred a good half hour to an hour after my last post to Mouser regarding Error 12035.

[IainB]

@mouser: Re CHS DBISAM Engine Error # 11949.
Over the last couple of weeks, I have been getting this CHS DBISAM error recurring - I have been hammering CHS a bit lately.
The symptoms seem to be precisely the same as DBISAM errors I have experienced before. The occurrence, whilst initially relatively infrequent, has become more (and annoyingly) frequent.
I have seen no text errors occurring in the database records.

This is a copy of the text in the error window:

---------------------------
Error..
---------------------------
DBISAM Engine Error # 11949 SQL parsing error - Expected column name but instead found tomato in SELECT SQL statement at line 1, column 62
---------------------------
OK  
---------------------------

Is there anything you would like to know about them when they occur?

What would you recommend I do? I have not repaired the database. I just stop and restart CHS when it occurs.

Update 2010-07-08: I have tried the Repair, and the "restore clipboard chain", but neither seems to prevent a recurrence of the error.

[tomos]

Well,
after a break of about a year (or probably more), I'm using CH+S again - without any error messages (knock on wood, etc)
Still on XP - did install SP3 since last use of CH+S.