>>Victor,
>>
>>There is a framework that comes with VFP but it's not as extensive as Maxframe. I would go ahead with Maxframe. I would also recommend learning as much as you can about client/server before you go much further. Keep in mind that all data access will have to be through remote views or SQL pass-through. If there's any place in your application where you USE a .dbf or do a SELECT from a .dbf rather than a view, it won't work in a client/server system without modification. Also, the upsizing wizard is a good start but there are several issues around upsizing that it doesn't deal with.
>>
>>>I don't have a beta version - so bare with the questions....I've heard that VFP6 comes with a bunch of new classes, enough of them that you can call it a framework. I'm about to start developing a new app and I need to decide a few things. It will have to be client/server ready at some point (soon). I figure since I've been using MaxFrame I would use it, then try the 'upsize wizard' (something new to me as well). Its my understanding that since MaxFrame uses local views that upsizing isn't all that difficult. In other words, I'd be writing the app in two steps. What I'm wondering is if I should do that or wait until I can get VFP6 and use it's framework (if there really is one), or if I'm going about this all wrong and there is a better way. Does anyone have any thoughts on this? Any ideas/suggestions would be a big help. Thanks.
>
>
>Also, things like SEEK, SCAN, etc won't work except on the result set...and you'll have to index it for SEEK to work.

True. Of course, if you don't use a .dbf you won't have to worry about any other operations like these