RE: VFP and SQL SERVER

Author: Nancy Folsom

Posted: 2001-05-30 at 14:41:16

J. Maurice-

> We have a very big app under VFP (may be 200 tables), 50 projects, no

> documentation (!), no notes in the prg (!!), written by different

> peoples at

> different times, ...

>

> After a period of 'revamping' (I mean that I am going to try to

> improve the

> app may be for 6 months), my customer want to have a C/S version with

> Pervasive and/or SQL SERVER. Do you think it is a hard work ? What he want

> to know is : will it take a day, a month, a year, a century ???

Okay, now for the correct answer <bg>. You don't know, and neither does

anyone else here. However, what you do know is that you have, probably about

a month, give or take, of fulltime work to do the functional

specification/requirements gathering which _will_ tell you how long it will

take and what implementation makes the most sense for your client.

If you have a 3 story house that needs to be remodeled, and you ask me how

long will it take, I'd tell you that first we need some plans, we need to

know where you're going, what you've got, and what can be reused. _Then_ you

get a bids on doing the construction, yes? It doesn't really tell me much to

say it's 3 stories and has has 4 bedrooms. I don't know what shape the

wiring is in, if there's termite damage, or whether you want cosmetic

changes or major floor plan changes.

So, the best situation is to contract to do the functional specs and req.

gathering at the end of which you and your client have a blueprint you can

study and use to specify the implementation. For example, he/she might find

that a SQL-Server solution will be too many $$$$ and staying with Fox, but

planning for an upsizing later will make the most sense.

This does NOT cost more money--design happens whether you plan for it not,

the only question is will it be good or will it be thorough, or will it

drive everybody on the project nuts? This does NOT add more time, either,

because design happens, either in the beginning before code has to be thrown

out and then incrementally thru the life of the project, or it gets done

over and over and drives everyone nuts. See above.

-Nancy

©2001 Nancy Folsom