VFP database stability

What's the VFP 8 database stability? I tried (long time ago) to work on i'ts
database in version 4.0 and and it was terrible (constant damages and
inconsistency) - since then I work on plain dbf. Is it in version 8 any
better? And btw what about fpt files in this version (fpt files often loses
their record links with dbf's).

Jader

Stefan
Fri Jan 07 02:40:31 CST 2005

Nothing particular. When you scroll through the NGs, you'll probably won't
find many threads about data corruption.
In general, with any file server approach crashing clients can corrupt shared
files. With a client/server backend, (well designed) clients can not.

In VFP you've got the choice to use native tables or any ODBC / OleDB
backend, like DB2, Oracle, MySQL, SQLServer/MSDE etc.
Client/server is more "expensive" regarding design / setup / maintenance
(and license fees depending on the RDBMS)
The VFP8 runtime and IDE are extremely reliable. Vfp9 was just released
to manufacturing a few weeks ago and looks promising. (FWIW, there
was no version 4.0)


hth
-Stefan

"Jader" <jader.usun@pbpolsoft.com.pl> schrieb im Newsbeitrag
news:crlf66$fp3$1@sunflower.man.poznan.pl...
> What's the VFP 8 database stability? I tried (long time ago) to work on i'ts
> database in version 4.0 and and it was terrible (constant damages and
> inconsistency) - since then I work on plain dbf. Is it in version 8 any
> better? And btw what about fpt files in this version (fpt files often loses
> their record links with dbf's).
>
> Jader
>
>

Esparta
Fri Jan 07 02:48:06 CST 2005

Hi Stefan

>(FWIW, there was no version 4.0)
AFIR There was an VFP 4 Beta



Stefan Wuebbe wrote:
> Nothing particular. When you scroll through the NGs, you'll probably won't
> find many threads about data corruption.
> In general, with any file server approach crashing clients can corrupt
> shared
> files. With a client/server backend, (well designed) clients can not.
>
> In VFP you've got the choice to use native tables or any ODBC / OleDB
> backend, like DB2, Oracle, MySQL, SQLServer/MSDE etc.
> Client/server is more "expensive" regarding design / setup / maintenance
> (and license fees depending on the RDBMS)
> The VFP8 runtime and IDE are extremely reliable. Vfp9 was just released
> to manufacturing a few weeks ago and looks promising. (FWIW, there
> was no version 4.0)
>
>
> hth
> -Stefan
>
> "Jader" <jader.usun@pbpolsoft.com.pl> schrieb im Newsbeitrag
> news:crlf66$fp3$1@sunflower.man.poznan.pl...
>
>> What's the VFP 8 database stability? I tried (long time ago) to work
>> on i'ts
>> database in version 4.0 and and it was terrible (constant damages and
>> inconsistency) - since then I work on plain dbf. Is it in version 8 any
>> better? And btw what about fpt files in this version (fpt files often
>> loses
>> their record links with dbf's).
>>
>> Jader
>>
>>
>

Stefan
Fri Jan 07 03:53:18 CST 2005


Oh!, but wasn't that an unofficial term and turned out to be
called Vfp5 when it was released to manufacturing later?

Saludos
-Stefan

"Esparta Palma" <espartaQUITAESTOPRIMERO@softhome.net> schrieb im Newsbeitrag
news:uo8rcWJ9EHA.2552@TK2MSFTNGP09.phx.gbl...
> Hi Stefan
>
> >(FWIW, there was no version 4.0)
> AFIR There was an VFP 4 Beta
>
>
>
> Stefan Wuebbe wrote:
>> Nothing particular. When you scroll through the NGs, you'll probably won't
>> find many threads about data corruption.
>> In general, with any file server approach crashing clients can corrupt shared
>> files. With a client/server backend, (well designed) clients can not.
>>
>> In VFP you've got the choice to use native tables or any ODBC / OleDB
>> backend, like DB2, Oracle, MySQL, SQLServer/MSDE etc.
>> Client/server is more "expensive" regarding design / setup / maintenance
>> (and license fees depending on the RDBMS)
>> The VFP8 runtime and IDE are extremely reliable. Vfp9 was just released
>> to manufacturing a few weeks ago and looks promising. (FWIW, there
>> was no version 4.0)
>>
>>
>> hth
>> -Stefan
>>
>> "Jader" <jader.usun@pbpolsoft.com.pl> schrieb im Newsbeitrag
>> news:crlf66$fp3$1@sunflower.man.poznan.pl...
>>
>>> What's the VFP 8 database stability? I tried (long time ago) to work on i'ts
>>> database in version 4.0 and and it was terrible (constant damages and
>>> inconsistency) - since then I work on plain dbf. Is it in version 8 any
>>> better? And btw what about fpt files in this version (fpt files often loses
>>> their record links with dbf's).
>>>
>>> Jader
>>>
>>>
>>

Jader
Fri Jan 07 04:35:20 CST 2005

Uzytkownik "Stefan Wuebbe" <stefan.wuebbe@gmx.de> napisal w wiadomosci
news:O7bf18J9EHA.208@TK2MSFTNGP12.phx.gbl...
>
> Oh!, but wasn't that an unofficial term and turned out to be
> called Vfp5 when it was released to manufacturing later?
>

May be you are right. I can only remember, it was after 3.0, and not for
very long because 6.0 has a lot better fuctionality and stability :)

Jader

frederic
Fri Jan 07 07:38:36 CST 2005

Bonjour Jader

1996 There was never a released version called VFP 4.0. What started out to
be VFP 4.0 in the beta process ended up becoming VFP 5.0 as Microsoft
decided to synchronize the version numbers for VB, VC++ and VFP, when it
went into Visual Studio. Its prerelease codename was Renard.

Fred
PS:from the famous www.foxprohistory.org


Pour mémoire, tu nous as écrit :

> Uzytkownik "Stefan Wuebbe" <stefan.wuebbe@gmx.de> napisal w wiadomosci
> news:O7bf18J9EHA.208@TK2MSFTNGP12.phx.gbl...
>>
>> Oh!, but wasn't that an unofficial term and turned out to be
>> called Vfp5 when it was released to manufacturing later?
>>
>
> May be you are right. I can only remember, it was after 3.0, and not for
> very long because 6.0 has a lot better fuctionality and stability :)
>
> Jader


--
- Fred
FE AVP&Cie
MS VFP MVP
email : http://cerbermail.com/?jWyjWqURpf
Membre actif d'AtoutFox,
Communauté Francophone des Professionnels FoxPro
http://www.atoutfox.org/
*-- VFP9 Beta disponible gratuitement
Téléchargez la ici : http://msdn.microsoft.com/vfoxpro/
http://www.foxforum.net/
http://www.foxprofr.com/

Craig
Fri Jan 07 12:26:40 CST 2005

Stability of VFP tables is more a factor of hardware and application design
than VFP itself. Always use data buffering...never directly edit a table.
Make sure the server, workstations, network cabling, etc are up to spec and
in good repair. Train users to exit the program...don't just turn off the
PC.

--
Craig Berntson
MCSD, Visual FoxPro MVP
www.craigberntson.com
Salt Lake City Fox User Group
www.slcfox.org
www.foxcentral.net


"Jader" <jader.usun@pbpolsoft.com.pl> wrote in message
news:crlf66$fp3$1@sunflower.man.poznan.pl...
> What's the VFP 8 database stability? I tried (long time ago) to work on
> i'ts
> database in version 4.0 and and it was terrible (constant damages and
> inconsistency) - since then I work on plain dbf. Is it in version 8 any
> better? And btw what about fpt files in this version (fpt files often
> loses
> their record links with dbf's).
>
> Jader
>
>