Whilst RDBMS allows easy direct manipulation of the database through products like .Net, the reality is that it is a nightmare if not thought out properly. If the business logic is in the client and you have a 1000 pcs, then a change to the business logic has to be sent out to 1,000 pcs at once. Then there is the issue of PCs being restored or offline when the update is occurring. If the business logic is at a central site, then it only has to be changed once. Also that same business logic could be reused for web services, web sites, mobile devices etc. This is why U2 is so strong as it has a powerful business rules programming language that runs at the database, that far outstrips the database programming languages of RDBMS. Whilst SQL Server allows .Net to be a business rule language they also warn of the performance hit.
Those dealing with RDBMS usually implement an application server, which hosts the business rules at a central site in a friendlier programming language than what the database has. For U2 the application server is combined with the database, instant cost and performance saving. Whilst it may be simple to link a dataset to a database and drag and drop it to text boxes on a client, one can be creating a rod for their back as business logic on the client will be a nightmare to support. What many do is link the dataset to a subroutine output thus keeping the logic on the database. If people want to link datasets directly to the database in .Net/java then they should look at 3 tier client server with this being done in the middle tier (application server) Just my 2c on this subject Regards David Jordan ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
