Posted by Sanders Kaufman on 11/18/06 12:24

I worked several FoxPro jobs with similar problems,
in converting it to an SQL server.

The first step, of course, is to create a database
diagram - and they (all of 'em) flat-out could NOT
get through that.

I finally came to the conclusion that the only way
to do it is to, behind the current IT group's back,
hire someone to reverse engineer what's in place.

Technically - it's totally doable if you stick to
the academics of software architecture.
Politically - it's a nightmare because FoxPro folks
tend not to GET server-based SQL.





Chris Marsh wrote:
> Alex,
>
> This post might be too late for you but I am the owner of a database company
> that began in VFP and now is in both VFP and SQL. It's a MASSIVE
> undertaking - far more expensive that you will even budget in your wildest
> dreams. MS will tell you lots of things work but depending on how you did
> your work in VFP then you might be looking for a tall building to jump from.
> The leap to SQL was good once we got there however getting there nearly
> killed us all. If you or your CEO would like to contact me directly I will
> be happy to give 10 - 15 minutes of advice.
>
> Chris (cmarsh@synergy-intl.com)
>
> "Alex S" <asluiter@gmail.com> wrote in message
> news:1162339883.402723.214630@m7g2000cwm.googlegroups.com...
>> Hello everyone,
>> My company uses a FoxPro database right now as an interface
>> and a database. For our situation, I have come to the conclusion that
>> it would be a better choice for us to move to an SQL server of some
>> sort. I have been given the task of overseeing the overhaul on the
>> program. I am paranoid about security and uptime, and so is the CEO and
>> there is more and more demand for the company to get on the interactive
>> internet. I'd like our clients to be able to submit data to our
>> database and pull data from it (only certain data of course). My idea
>> is to convert the FP tables to and SQL server and write an internal
>> application(or web-based - advantages? I dunno) for the interface. For
>> the internet side of things, my idea is to have seperate web database
>> (SQL) that will put information from web clients. Through the internal
>> interface, internal users would then be able to pull data from the web
>> database to the internal SQL. And through the internet (authenticated
>> of course), the web users would pull data though the web database, who
>> pulls information from the internal SQL database. Would someone please
>> tear this idea apart w/ advantages and disadvantages. Also, if this is
>> the best route, tell me how I can sell this idea to my boss. What's so
>> good about using SQL vs. FP over the internet? What about internally?
>> What about security? Cost is going to place a big role on the what the
>> CEO decides, unless I can sell him otherwise. Should I tell him that we
>> shouldn't do it now and save some money to do it right? Or what? Some
>> help please. Thanks.
>>
>> Alex
>>
>
>

[Back to original message]