I agree with the previous comments, but I'll throw in a couple of opinions to the mix <g>.

I like automobile analogies, because everybody understands them.

In this case, I have sometimes asked, "If we have a '93 Chrysler, but what we need is a 2001 model, would it be best to upgrade it part-by-part until the '93 has evolved into an '01 model? Or would that approach end up taking more time, more money, and resulting in a lower-quality product?" And what if the '93 model is already in a state of disrepair? Should we start with it as a baseline, and build up from there?

If the manager's response goes something like, "... well, it's not all that bad, you can just fix things as we find them...", then suggest that you perform a "quick" audit of the application, to determine what works, what doesn't, what needs it does not meet, and to get an estimate of the proposed project. Include the needs of end users, executives (consumers of the data pumped out of the system), and developers.

Once you have an objective document, get with the manager to prioritize the problems and needs. Then prepare cost estimates for a rewrite vs. their original approach.

As you pointed out, this is a communcation problem. Let the manager know that your objective is to make sure that you know what he/she knows, and vice versa, so that an informed and mutually agreeable approach can be decided upon.






>I have inherited an Access based program which is a mess. The primary database contains links to at least 7 other mdb files using direct paths i.e. n:\ucs\data\*.mdb. There are over 400 different tables between all of the db's; as well as forms, queries, reports, and macros that number in the multiple hundreds as well. The program is used heavily by around 75 people a day, 25 at any given time. The database in general has a very poor design and has been a work in progress which has been patched and added to more times than worlds largest quilt. Needless to say it is becoming more and more unreliable every day.
>
>The decision has been made to upgrade the Access database to use SQL Server. I believe that a new database needs to be created and the old data imported in so as to not lose any data while improving performance. I also believe that the program itself should be rewritten using VFP as a front-end. I realize this would be a big job but I think it is the right way to do it. The powers that be think that we should upgrade one table or section at a time and continue to use Access databases for the front-end and simply link to the SQL server.
>
>Correct me if I'm wrong but client-server programming is a different paradigm than that of fileserver programming which requires a completely different kind of thinking. What I need is arguments either way. This program will probably be distributed to other locations so I am also looking for portability in this product.
>
>Your ideas will be very much appreciated.
>Kris H.