[AccessD] LINQ

Hi Arthur

As I understand it, LINQ is rather an attempt to create a database vendor independent query class in dot net, thus this should be within the thoughts of Dr. Codd as you reference these (I haven't read his books). You may argue that, if so, you are still trapped, now in dot net, and that may be true but only until the Mono project (dot net for Linux) catches up on this.

Neither do I like to be trapped with MS-SQL. That's why I never have made an ADP (except for fun) and never will.

As to the business logic, I think it should be kept in the front end for the simple reason that it is much easier to maintain a frontend than a database engine, the only exception being if performance seriously calls for it. If having the business logic in the frontend for some reason is not practical - say, when using several different frontends - business logic could be moved to a middle-tier. The only logic I prefer to place in the database itself is low level routines like validation and other rules that will "never" change. Never is a dangerous word, but a field for a month value will never be smaller than 1 or larger than 12 and a year value will not be larger than 9999.

When I listen to MS at the developer meetings it is perfectly clear that while examples etc. are, of course, shown with their own engine, MS is fully aware that "out there" many Oracle and DB2 installations exist and dot net must serve these as well.

/gustav

>>> artful at rogers.com 09-10-2005 01:01:14 >>>
Call me an old-timer if you wish, but I do think this is NOT hot, but rather
an extension that attempts to trap developers in MS-SQL.