john hilton wrote: > I would jump into whichever made a generic SQL backend
Unfortunately, there's no such thing as generic SQL. There was a standard (SQL99) that all were going to comply with but this never happened. Microsoft are the worst offenders (surprise). For example, almost every SQL database calls the date and time data type TIMESTAMP. Microsoft once used TIMESTAMP, but for reasons that I can't reconcile, said bugger it, we'll change and call it DATETIME. So every line of code in a package like Totalcare or Profile that can use multiple DBMSs has to have an IF loop every time it wants to work with a date or a time (this is one example, there are many others) - an incredible amount of bloat has to be added - all because Microsoft's way of dealing with competition is to purposely not comply with standards. regards, Peter. _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
