What Jim said -- the database software isn't the issue.=20 1. Get a definitive list of requirements from the customer. 2. Fix or rewrite the front end. MSFT makes SQL glue for most any language = if you choose not to use VB, C#, F#, etc. 3. You can choose to re-implenet the backend with another product, but a pr= operly set up MSSQL db will perform just fine. -Pete On Dec 16, 2011, at 1:10 AM, jimf@webstudios.co.uk wrote: >=20 >=20 > I'd tend to disagree with you here. MSSQL isn't 100% crap; the > code/design that the prior "developer" may have created > could well be crap, but the MS version of SQL isn't to blame for > that. =20 >=20 > I am sure that a reasonably untalented developer could make a pigs > ear from any environment..=20 > *(I am working on one right now!)=20 >=20 > I would approach this from a slightly different angle. Discover > what the client does / does not like about the system (apart fromt > the instablity that is). > and redevelop the front end first..=20 > On Fri 16/12/11 12:37 AM , V G x.solarwind.x@gmail.com sent: > Hi all, > I'm doing a project for a doctor whom previously employed a highly > unskilled and incompetent contractor whom used Microsoft SQL Server > 2005 for a patient database. I now have to pick up the pieces and > write a program that accesses the database. The problem is, ms sql > server is 100% crap, and the visual basic program that the previous > dude wrote is even worse. The way that the database is, is very > inconvenient to use (for me as a developer) and constantly errors > out, > crashes, etc on several systems I've tested, as well as in a VMware > environment. I need to convert it to PostgreSQL (or MySQL at the > worst > case) as soon as possible as the doctor's patients depend upon it. I > only need to keep the table structure (column names and types (or > similar types)) and the primary and foreign keys. Functions and > views > are not necessary as I can make those myself later on. > Q: Anyone know of any programs or methods to reliably convert the > database data from ms sql 2005 to PostgreSQL (or MySQL if I don't > have > an option)? There's a LOT of data, so manually copying it is out of > the question. > --=20 > http://www.piclist.com [1] PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist [2] >=20 >=20 > Links: > ------ > [1] http://www.piclist.com > [2] http://mailman.mit.edu/mailman/listinfo/piclist > --=20 > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .