> I do have a couple questions though. Have one customer that wants to > develop a huge database that will evetually be distributed on CD and > online. I am thinking using a regualr database now to build his project > (Access or something similar) and then migrating to Oracle or SQL server. > I was wondering if the database in StarOffice would be acceptable for this.
No. Use postgresql. Please define what a "regular database" is? That doesn't make sense suggest starting a project in a local office-suite, bundled DB and later move it to a production quality DB. Especially when you know the end result is a need for a powerful database now. That's like saying when designing a software project for encrypted stock market transactions we should start the whole thing in csh scripts and then eventually migrate that into a C++ program. That's not how development is supposed to work. Sadly sometimes things like that happen because the decision makers are misinformed. Happens in the development world I guess. Use postgresql. /me is done with the postgres plug. cheers, Andy
