Database Engine Error -38

A place for users to ask each other questions, make suggestions, and discuss Bookends.
Post Reply
jbri
Posts: 5
Joined: Wed Aug 08, 2007 1:16 pm

Database Engine Error -38

Post by jbri »

What does "Database Engine Error -38" mean?

I am finished with my thesis (which is due in two days) and wanted to do a test scan of just one paragraph in Mellel (with a mere three references). Nothing can be scanned, all I get is the above error message from Bookends.

I have verified the database (and told there are no problems), I have rebuilt it, got the same error message, and I have repaired it and also get the same message.

Running: Mellel 2.2.7.1 / Bookends 10.1.2 / OS X 10.4.11


TIA
jbri
Posts: 5
Joined: Wed Aug 08, 2007 1:16 pm

update...

Post by jbri »

After posting my message, I tried closing Bookends and the window with said error message popped up again and my entire system crashed (which is a rare feat indeed).
I rebooted, repaired the system's permissions and wiped all the maintenance scripts. Have now done two successful test scans.
I would still like to know what the error message means, though. It's not mentioned in the manual.

On an entirely different note: after scanning just now, I noticed double colons in every reference. When I did a test scan last month, that didn't happen (i.e., Author 2006:: p. 58) I'll check the manual again, but if anyone knows off the bat what that's about, I'd appreciate a shout.

Cheers
Jon
Site Admin
Posts: 10293
Joined: Tue Jul 13, 2004 6:27 pm
Location: Bethesda, MD
Contact:

Post by Jon »

That's a Mac OS error.

-38 = fnOpnErr = File not open

As for the double colons, check your format. It looks like you're using cited pages, and it may be that 2 colons are entered in the field that is output before the pages.

Jon
Sonny Software
jbri
Posts: 5
Joined: Wed Aug 08, 2007 1:16 pm

Post by jbri »

Thanks, Jon. Yeah, after the system crashed, I thought it might be the mac.

The double colon thing must be my own mistake. Whenever I cited pages over the last few months I always put a colon after the @
Now I take it from the manual that that was unnecessary. Everything else looks good though, at least at the moment.

Cheers
Post Reply