> 	I'd tend to disagree with you here.  MSSQL isn't 100% crap; the code/des=
ign
> that the prior "developer" may have created  could well be crap, but the =
MS version
> of SQL isn't to blame for that.

I would agree with this. We use MS SQL to allow multiple parties access to =
our OrCad parts database, through OrCad CIS, and have never had an SQL hicc=
up that I am aware of (although I am not the database administrator).=20

I also suspect that any problems with the database are probably the front e=
nd, although there may be problems with the way the tables are laid out and=
 linked (i.e. bad database design) rather than a fault with the MS product =
itself.


--=20
Scanned by iCritical.

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.