>>I have been testing Sybase Anywhere (previously WATCOM SQL) for a while here on Novell and WIN95 standalone. I have always been impressed by its superb SQL grammar and low-pricing.
>>
>>However earlier versions were unusable with VFP3 (lots of bugs related
>>to VFP, sybase or ODBC or the 3 of them, don't know).
>>
>>But I found that the most recent version downloaded from sybase web site was really easy to set up (in minutes), easy to administer and
>>the product seems to cooperate with the Fox Enfin!
>>
>>Possible I should to move ahead from test to production on midsize
>>databases but, up to know, i have found very little feedback
>>of Sybase except has a development companion product to PB.
>>
>>Has anyone real-life experience of the tool ?
>>
>>Thanks in advance
>>
>>François
>
>You want to use a local database product as a database for FoxPro???? Whatever for??? The FoxPro database engine is MUCH faster and none of the 'Anywhere' products can handle large databases any better than Foxpro.
>
>Up until 2.6, I could understand the frustration of some using Fox databases (tables) particularly because the Fox SQL was not ANSI standard. But 5.0 is real close to ANSI, so I don't understand why you would want to use another stand-alone product to support VFP. Even if it was AS fast (which it's not), I would still argue that having to go through an ODBC filter would be enough reason not to do it.
>
>I have also heard that both Sybase Anywhere and SQL Anywhere do not fully support CTLIB, as they both claim to. They both fall well short of the real thing.
>
>If you're using it as a development or demo companion...do it. They're both pretty good. But beyond that, I don't see any reason to do so.
>
>Matt

I take your point concerning FOXPRO as a super-fast engine.

In the field of application Ibut apart from speed
I see no reason to use vfp other than as local cursors to remote servers.

The reasons :
- I am working on modsize database (10 k records) where is never a blocking
factor,

- tHe kind of app i am working upon requires strong ANSI compliance.
fox implementation of ANSI SQL is extremly weak (check SQL SELECT statement
in SQL-92, SYBASE ANYWHERE or ACCESS ... compare)