I make 0x1904 = 6404 - 8404 is 0xD420. Unless I'm going crazy.
From: Jean MAURICE jsm.maur...@wanadoo.fr
To: ProFox Email List profox@leafe.com
Sent: Sunday, 10 November 2013, 6:59
Subject: Re: Foxpro/DOS not a dbf file error
I am glad to see that 'old
You are right !
Thanks
The Foxil
Le 10/11/2013 16:13, Laurie Alvey a écrit :
I make 0x1904 = 6404 - 8404 is 0xD420. Unless I'm going crazy.
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance:
On 11/10/2013 07:47 AM, Jean MAURICE wrote:
You are right !
Thanks
The Foxil
Le 10/11/2013 16:13, Laurie Alvey a écrit :
I make 0x1904 = 6404 - 8404 is 0xD420. Unless I'm going crazy.
all the hex math aside, the database in question has 6,403 records. :)
John
You are right ! ;-)
The Foxil
Le 10/11/2013 17:01, John R. Sowden a écrit :
On 11/10/2013 07:47 AM, Jean MAURICE wrote:
You are right !
Thanks
The Foxil
Le 10/11/2013 16:13, Laurie Alvey a écrit :
I make 0x1904 = 6404 - 8404 is 0xD420. Unless I'm going crazy.
all the hex math aside, the
Sounds like Cryptlocker to me. exactly what I got last week Hope I'm
wrong for your sake.
Dave
-Original Message-
From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of John R. Sowden
Sent: 09 November 2013 19:33
To: profox@leafe.com
Subject: Re: Foxpro/DOS not a dbf file
We had a computer freeze during the night (it gets cold in the SF Bay
Area), and the worker was doing data enter into a dbf using foxpro/dos
2.6, under program control. I flush the buffer after every record
entered, due to some 'segment errors' of yesteryear. Now we cannot get
back into the
On Sat, Nov 9, 2013 at 10:42 AM, John R. Sowden
jsow...@americansentry.net wrote:
We had a computer freeze during the night (it gets cold in the SF Bay Area),
and the worker was doing data enter into a dbf using foxpro/dos 2.6, under
program control. I flush the buffer after every record
On Sat, Nov 9, 2013, at 06:53 PM, M Jarvis wrote:
On Sat, Nov 9, 2013 at 10:42 AM, John R. Sowden
jsow...@americansentry.net wrote:
Now we cannot get back into the dbf because
it comes up as a 'not a dbf' error.
I hope it ain't Cryptolocker ...
If you have VFP you set tablevalidate to 0 and try to open the table
If you can, append an empty record, delete it, pack the table and
recreate the index.
I do that with old fox dos tables and it usually works
Rafael Copquin
El 09/11/2013 15:42, John R. Sowden escribió:
We had a computer
May be it is due to a wrong record number in theheader of the file. I don't
rememberin wich bytes it is (and it is in a 'reverse mode' ?) and try to add 1
to it (or minus 1).
When the computer freeze, may be the 'last' record was added but it has no time
to update the header.
HTH
The Foxil
Collapse imageTable Header Record Structure
Byte offset Description
0
*File type:*
0x02 FoxBASE / dBase II
0x03 FoxBASE+ / FoxPro /dBase III PLUS / dBase IV, no memo
0x30 Visual FoxPro
0x31 Visual FoxPro, autoincrement enabled
0x32 Visual FoxPro, Varchar, Varbinary, or
03 0D 0B 09 04 19 00 00-21 01 4B 00 00 00 00 00
03 : foxpro dbf without memo
0D 0B 09 : last update november, 9th 2013
04 19 00 00 : number of records : 4868
Try to write 05 or 03 instead of 04 in byte n° 4 (beginning with 0)
HTH
The Foxil
___
I have used the recovery tools from abri for years.
http://www.abri.com/
jerry
-Original Message-
From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Jean MAURICE
Sent: Saturday, November 09, 2013 1:20 PM
To: profox@leafe.com
Subject: Re: Foxpro/DOS not a dbf file error
On 11/09/2013 11:09 AM, Alan Bourke wrote:
On Sat, Nov 9, 2013, at 06:53 PM, M Jarvis wrote:
On Sat, Nov 9, 2013 at 10:42 AM, John R. Sowden
jsow...@americansentry.net wrote:
Now we cannot get back into the dbf because
it comes up as a 'not a dbf' error.
I hope it ain't Cryptolocker ...
On 11/09/2013 11:09 AM, Alan Bourke wrote:
On Sat, Nov 9, 2013, at 06:53 PM, M Jarvis wrote:
On Sat, Nov 9, 2013 at 10:42 AM, John R. Sowden
jsow...@americansentry.net wrote:
Now we cannot get back into the dbf because
it comes up as a 'not a dbf' error.
I hope it ain't Cryptolocker ...
On 11/09/2013 11:25 AM, Jean MAURICE wrote:
03 0D 0B 09 04 19 00 00-21 01 4B 00 00 00 00 00
03 : foxpro dbf without memo
0D 0B 09 : last update november, 9th 2013
04 19 00 00 : number of records : 4868
Try to write 05 or 03 instead of 04 in byte n° 4 (beginning with 0)
HTH
The Foxil
Thank you all for your input. Sorry for the delay, had to repair my
wife's car. Anyway I needed a hex editor that would work on fat32.
Found uhex.zip. It is part of the freedos family of programs. Per
suggestion, I changed the 5th byte (byte 4) from 04 to 05 assuming that
the added record
I am glad to see that 'old science' is still alive !
04 19 00 00 : number of records : 4868
I made a mistake, 19 is hexadecimal so number of records should be 8404 ...
Regards
The Foxil
___
Post Messages to: ProFox@leafe.com
Subscription
18 matches
Mail list logo