>Sybase had a booth at the SW Fox (great conference BTW), where they were talking about working on support the foxpro DML, things like seek, scan, recno(), etc. Does this seem to people like it would be doable? It seems to me like it help greatly in the transition to C/S and the maintenance of a code base that talks to both a C/S backend and native foxpro. Any thoughts?

I wonder what they are up to. Are they looking to map VFP commands (SCAN/SEEK/LOCATE/FIND...) to Sybase backend somehow, and if they are, they would need to tweak the VFP binaries, which they really can't (practically or even legally) do. If they are looking to do these things through Sybase specific function calls, that might be interesting, at least in the "academic" sense.

In the meanwhile, and maybe regardless, using VFP remote views against a Sybase backend should accomplish the same thing with no add-ons and no backend-lock-in -worries (once you start down a Sybase -function call route, you are tied to their backend, unless of course you write another itermediate tier of some sort which can talk to Sybase but also to other backends without having to change code all over the place).

To me this seems like a somewhat useless excercise, but I may not grasp fully what they are trying to accomplish here.

IMO your best bet in moving your VFP apps to C/S is to simply start using remote views. It is the most "natural" and backend-independent way of doing things C/S.