>Thanks for the reply. A couple of questions.
>
>You say 'Using a solid backend database, and SPT in vfp you can keep'. What is SPT?

SPT, = Sql Passthrough - its the technology - using ODBC to communiate with a totally seperate Database Server. There are other options for VFP to communicate with other Database's like Remote Views, Off line Views.... But my experience, and some others in the the VFP community, tend to go with the tried and true SPT. ... (may I correct this. ) there is actually a debate over the ADO OLEdb , Remote Views / SPT. and so on, seems like that whatever someone gets used to and works for them, is the best.... So take my comment in context. Its just an opinion. I like SPT. Other devleoper like other methods... they all work.

There is a more complete discussion on the matter over on the wikis.. here.
http://fox.wikis.com/wc.dll?Wiki~Client/ServerDataAccessTechniques~VFP and here.

http://fox.wikis.com/wc.dll?Wiki~SQLPass-Through~VFP

These articles should help get you started...

Re upsizing, Sure there are wizards,... but once again, with applications, sometime what you get in the simplicity, is a lack of total control. There are products out there(other than the Wizards ) which do file conversations,. from vfp to sql statments. But which ones would be good, and really work, depends alot on what server you select. The backend server is your biggest choice here. Once that is decision is done, then the choice of tools becomes eaiser.

A framework. - Yes it could help. and once again, depening on what backend database. and so on.... Lots of discussions on when to use frameworks. pro's cons, but for the most part, the more a system becomes conmplex, and out of the hands of one developer... then it usually time to start looking at some sort of framework. A framework will also help in keeping the connections between vfp and whatever you backend is going to be. Those commands are writen, tried and work.... otherwise, you have to write your own.

Framwork Questions, Ill pass those onto someone who really knows. and has worked with them. more than I have. re how easy. and so on ....


>
>I would definately hire someone to look at the options. But are there any products that help you convert a VFP file server application to a VFP Client/Server application?
>
>Would a framwork help here? Is it hard to retrofit an application into a framework? Then once you have the application in the framework is it easier to go client/server and to change your backend database?
>
>Thanks
>
>Brenda
>
>
>>
>>You have a few options.
>If your users can handle Fox pro - like 2.5 style.
>http://www.recital.com/
>might give you an option worth looking at... Depending on how your GUI looks, >it may or may not be an option.
>>
>>I put my app on the web about 2 years ago. (still using that way today.) the results of many hours of learing php, html, web forms and so on. It really gives the users. a satificatory result. Not Great, but not bad. Its actually >the quickest way to get your app on the net.
>>
>>However, Client server, is the real Key to a GREAT VFP application. Using a solid backend database, and SPT in vfp you can keep all your well worked out reports and forms, keeping the look and feel of your app. Rewriting you most if >not all the underlying code.
>>
>>its not pretty, or easy. to start in that direction. But the results. Are great. There is a pretty steep learning curve, But once you get some of the >basics down. it starts to move quickly.
>>
>>As Cindy mentiond you might consider getting some outside help getting you started, and suggest a Solution. but my 2c says, go client server. VFP is a great frontend client. The the choice would be what backend. SQL server, >Sybase, oracle. That becomes a matter of cost. and other considerations.
>>
>>Bob Lee
>
>>>I have a medium sized application written in VFP 6.0. There are approximately 45 free tables, 100 forms, 40 reports, and 100 programs. The app was converted from FoxPro. The core was rewritten when moved to VFP but the fringe forms were simple converted from FoxPro to VFP. Anyway the app is a hodge podge. It is installed at about 30 sites and each site has about 5 clients who each access it over the Novell network.
>>>
>>>Now my baby, and I, need to grow up. My company wants to move from 30 sites to a single site with a centralized database. Currently the response time on my application is too slow to allow all my clients (which are in FL, GA, TN, VA) to access a single copy of my application. My company is also throwing out buzz words like Sybase, SQLServer, Unix - but nothing is offical.
>>>
>>>I am at a lose as to what to even start researching. Intranet, Client/Server, whatever. Where should I start looking for answers?
>>>
>>>Thanks
>>>
>>>Brenda