Search results for query: *

It's even worse than Mirtheil said: when Btrieve deletes a record, it completely zeroes out all the bytes of the record so that even if you knew the exact disk address, you would find no data there. It's been this way since Version 1.0 way back when, and was done deliberately as a security...

Oops! That post I found about a macro to automatically save pages was on another site altogether! I've not found anything comparable here but haven't checked every post in this forum yet...

I make extensive use of macros in Word, to enforce my Style Book rules for a 40-page quarterly magazine that I handle for a nonprofit of which I'm a director, and would like to do the same in Publisher 2002 which is what I provide to our print shop. However documentation for the VBA and the...

Those additional 8 bytes offset in Version 7 and 8 files (and later) are the hidden "system id" timestamp, I believe. Your presumption for the first 2 bytes is almost correct; it's a reference count that serves as a deleted-record flag also. The FCR offset is the starting point for any...

I also can confirm that both can run at the same time on the same system. I have both on my laptop, and they both start as services when I boot it. No problems noted. The only possibility of trouble that I can see would be if the server's resources are not adequate for both packages. My laptop...

What shows up if you look at the field as an 8-byte integer? At least one commercial application that I often do data recovery for uses this data type for dates, storing today's date as 20060813 instead of using Btrieve's own date type. It's also possible that the field may be stored as a...