Is there any limitation on the table size ?
Thanks,
Edward
You can read about the table size limitation in the Help at "Visual FoxPro
System Capacities". Please note that the 2Gb limit is per file so you can
have 2Gb for the table, 2GB for the memo and 2Gb for the index.
--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.wi...@mvps.org http://cindywinegarden.adsl.duke.edu
http://msdn.microsoft.com/vfoxpro http://foxcentral.net
"Edward" <edw...@edihk.com> wrote in message
news:062801c2f597$9b7a1010$3401...@phx.gbl...
C> There are commercial tools, but most of the time you can fix it yourself
C> with the Hex Editor that comes with VFP.
Comes with VFP??? Which Hex Editor? What? Where?
Looking forward to hearing from you!
WBR,
Willianto
Try C:\Program Files\Microsoft Visual FoxPro 8\Tools\HexEdit\HexEdit.app or
a similar location for VFP6 and VFP7.
--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.wi...@mvps.org http://cindywinegarden.adsl.duke.edu
http://msdn.microsoft.com/vfoxpro http://foxcentral.net
"Willianto" <will...@remove-me.telkom-and-me.net> wrote in message
news:uoYBR4y...@TK2MSFTNGP12.phx.gbl...
Thanks anyway!
WBR,
Willianto
"Cindy Winegarden" <cindy.wi...@mvps.org> wrote in message
news:#pMwkqz9...@TK2MSFTNGP11.phx.gbl...
There is no command or utility that automatically fixes a damaged table
file. Your best option is to use a third-party tool. For third-party repair
utilities, take a look at this article:
87688 PRB: "Not a Database File" Error Using a Database File
http://support.microsoft.com/?id=87688
The file size limit for table is 2 GB. You can see all the VFP capacities
by search on System Capacities in the Help file.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
> There is no command or utility that automatically fixes a damaged table
> file. Your best option is to use a third-party tool.
Considering that you are one of Microsoft FoxPro Technical Support, can you
tell me why you guys have not create one? I mean, it's high time. The VFP is
on version 8.0 already. Version 9 is on the way.
WBR,
Willianto
"Lee Mitchell" <Le...@microsoft.com> wrote in message
news:9PjsxZ59...@cpmsftngxa08.phx.gbl...
>> There is no command or utility that automatically fixes a damaged table
>> file. Your best option is to use a third-party tool.
W> Considering that you are one of Microsoft FoxPro Technical Support, can
W> you tell me why you guys have not create one? I mean, it's high time.
W> The VFP is on version 8.0 already. Version 9 is on the way.
Because almost all corruption cases are not VFP guilt, but rather Hardware,
OS, Stupid Users problems. And there is absolutely no need in another one
DBF recovery utility, as there are a lot of them avaliable both as
commercial products and as freeware products. Moreover absolute majority of
them can repair only one rather simple problem - disparity in record counter
in DBF header and in data part of DBF file itself. And many other types of
corruption can't be eliminated automatically at all - they require very
competent specialist (familar with VFP, dbf file structure, and that is even
more important - with the program that use this tables). As for assisting
tools - HexEdit.app is pretty enough for any case.
Stop the war!
WBR, Igor
> Because almost all corruption cases are not VFP guilt, but rather
Hardware,
> OS, Stupid Users problems. And there is absolutely no need in another one
> DBF recovery utility...
Well, ok, but wouldn't it be nice if vfp has an internal command to repair
the dbf? VFP provide internal command to repair the database containers
(i.e. actually the dbf table) with VALIDATE DATABASE RECOVER. What about
adding a command, say, VALIDATE TABLE RECOVER?
> , as there are a lot of them avaliable both as
> commercial products and as freeware products.
Yes. I'm aware of the commercial products. But I couldn't find any freeware
products for dbf recovery, there is one in the UT but that's only fix the
old foxpro 2.5 dbf files. Can you point me to some of them?
> Moreover absolute majority of
> them can repair only one rather simple problem - disparity in record
counter
> in DBF header and in data part of DBF file itself. And many other types of
> corruption can't be eliminated automatically at all - they require very
> competent specialist (familar with VFP, dbf file structure, and that is
even
> more important - with the program that use this tables). As for assisting
> tools - HexEdit.app is pretty enough for any case.
Yup! And from my point of view, that gives me another 'job oppurtunities'
<g>
>
> Stop the war!
Agree! Stop the war!
WBR,
Willianto
"Willianto" <will...@remove-me.telkom-and-me.net> wrote in message
news:OTQWb5M#CHA...@TK2MSFTNGP11.phx.gbl...
Thanks Anders!
WBR,
Willianto
"Anders Altberg" <pra...@telia.com> wrote in message
news:uSJsbBR#CHA....@TK2MSFTNGP11.phx.gbl...
AA> In VFP8 a table validation is performe by defaultd when the table is
AA> opened. It compares the record count in the header to the actual file
AA> size and warns about a problem. It doesn't repair the table. SET
AA> TABLEVAIDATE TO 0|1|2|3
Good point, I was unaware of this enhancement.
But as for RECOVER, even if it will be added, I'd better not use it. I know
what is VALIDATE DATABASE RECOVER, it is useful, but it really don't REPAIR
my database, it only remove some information from there, that will let me
open tables and start real repair process, I have to write much more code to
perform correct REPAIR procedure.
Bobby