Hi Russell:

Sure, I think near to April / May we could have a window to do a presentation. We should stay in touch until then.



>Sam,
>
>I should have thought to ask this before now, but will you or anyone involved in this development effort be up Atlanta-way anytime soon or anytime this year? We'd love to have one of you do a presentation on the product at AFUG. Doesn't matter when you're here. We'll adjust our meeting date to fit your schedule.
>
>Russell
>
>>Hi Russell:
>>
>>As Tracy Pointed it is another backend and a good one. I also used that, but was somewhat disappointed because it did not fully support the VFP Tables.
>>
>>With Sybase now also supporting the VFP tables and even in Server Mode, you have more selling points for your choice of VFP tables, more on that below.
>>
>>We have something named the TableLayer, this is a fully extensible layer that lets you build your own TableRepresentations in a few lines. We used it to:
>>
>>1. Build a table layer for VFP9 using the VFP9 Runtime, this although tied to Windows x86, has the advantage of using your years old VFP9 Runtime.
>>
>>2. Create a TableLayer64 that breaks the VFP9 limits, as more than 2Gb tables and 1000 or more fields in a table between other things. This Layer is fully compatible with VFP9 Tables, as long, you don't break the VFP9 limits.
>>
>>3. Develop an ADO.NET table layer that let you use any ADO.NET DataTable as if it was just a VFP Table. Something like this:
>>

>>SQLUSEDataTable(oTable, "MyAlias")
>>SELECT "MyAlias"
>>SCAN
>>  *
>>  *  Play with the data as if it was a VFP table even indexing, seeking and all
>>  *  the usual VFP stuff
>>  *
>>ENDSCAN
>>

>>
>>4. More layers are coming...
>>
>>So with Sybase offering VFP9 DBFs support and the easy TableLayer mechanism, we have a third way to access VFP9 Tables, as the Advantage Local Server is free so you can use it as the underlying Table Engine. And it looks like they also break the 4Gb limit, so this means a broader and brighter future for your DBF Tables.
>>
>>Also with that we could potentially have a DB Server based in VFP9 tables. This is something We always wished to have enabled in VFP9 and it is something we have in our pipeline as "possible" Future Enhancements, although our plans in that regards are a little more ambitious than just a plain DB Server. This is a good selling argument to your use of VFP9 tables, now that those tables can be redeployed to a Server without changes.
>>
>>The above coupled with the JDBC Driver and the easy way that you can turn our compiler generated .NET IL Code into Java Virtual Machine Code (see Mainsoft or JACIL), means that even if you don't want to go the .NET Route with your VFP Code / Data, you can go the Java Route. In any case you can rest assured that your VFP Code and Data will work in any environment / OS, without having to depend of just a single provider Microsoft, Sybase or even eTecnologia.
>>
>>
>>. .
>>
>>>This is an interesting development:
>>>
>>>http://weblogs.foxite.com/andykramek/archive/2008/01/05/5530.aspx
>>>
>>>Does it / could it have any bearing on what you are doing?
>>>
>>>Russell Campbell