Advise on re-write of a database.

[mahenkj2]

We have one production database in which the front end Delphi 5 and backend SQL server 2005 has been used as communication software (Hopefully correct info). The database is the result of last several years continuous improvement and frequent additions of new requirements. Since, originally it was devised from a small end and so lacks some kind of flexibility etc. For a single change, we need to go to database developer.

There are two aspect of it, one is certainly cost but the other is the result sometimes is not as desired. Also, if developing in the hand of user (organization, not the clerk), we may get enough time to try and error to achieve the best results.

An initial thought is to rewrite this database. I never had any experience of access few months ago, but now my one of access database is running and we are happy to see the flexibility the access have. We expect same kind of user friendliness and flexibility in our production database.

Please advise us your expert opinions to way forward. How can we improve our production database.

About the production database - We are a manufacturing company and from raw material to finished stage, we track the product, its measurement results. all in this database. We think it is a very large database.

 

[G37Sam]

Sounds like you're in for an interesting project.

I've worked on something similar a while back but the project got scrapped. Started with Aluminum sheets and ended with cans and paint buckets. SQL Backend with an Access Front End. It can definitely be done that I can tell you.

The most important thing is a solid table structure in your BE

 

[ButtonMoon]

Are you considering rewriting the database or the application or both? Assuming you want to stick with SQL Server but potentially replace the Delphi application then a .NET or Java -based app is probably a more obvious upgrade path than Access. If a few months with Access is your only database development experience then you should certainly get some more experienced help to assess what needs to be done.

Wholesale rewrites can be expensive and risky. Years of work on the current solution presumably adds up to some significant financial and intellectual investment, so get some expert advice and be clear exactly what the business case and likely benefit is before you even think about writing code.

 

[mahenkj2]

Certainly, for this rewrite we are going to use some and hopefully same developer because he has worked for years on this database, but the apprehension is that should we use same delphi/SQL or some good alternatives are there.

 

[JLCantara]

I disagree with ButtonMoon: the combination Access - SQL Server does the job. I made and maintained an industrial production control system based on 1000+ objects (tables, views, forms, etc.). I never had any problem with the front end (Access). Note that in the trade, using Access is disregarded, some sort of a sad pittance for low-end programmer.

The application can be secured so that the average user can't break the code...

First, start with the DataBase, then move to the application, starting with the basic data.

If that person is not an Access expert, he will find that it's a long, long way to Tipperary. Such a project should be done by an Access expert...

JLCantara.

 

[spikepl]

As ButtonMoon wrote:

Wholesale rewrites can be expensive and risky. Years of work on the current solution presumably adds up to some significant financial and intellectual investment, so get some expert advice and be clear exactly what the business case and likely benefit is before you even think about writing code.

The business case will have gone through the various options/combinations of db and some frontend... To decide on Access or .NET or Delphi or Java is premature prior before going through all the pros and cons.

Also, the important bit is also to consider your needs 1-2 years down the road and work back from that.

If this is a business-critical app, then get advice.

 

[mahenkj2]

I thank to all the experts for sharing their opinion. I think, we should take some time for research on all the pros and cons. Since, it is a business application, so it is critical for us.

best regards.