2004-12-22, 08:21 PM
[b Wrote:Quote[/b] ]Really, the best solution in the long run is moving the items to a Access Stored Procedure. Â I like stored procedures for several reasons. Â Seperates the Data from the Business Logic, and the Presentation Logic. Â Plus allows for easier support of multiple databases.Separation of business logic from presentation is a good thing, but the same is true on the back end. Â Ideally, I never put any business logic in the database, unless performance dictates...
Stored procedures are not portable! Â Try migrating from SQL Server to Oracle!
All of my development now is strictly multi-tiered and the database does one thing and that is to hold and index data...
The logic goes in the middle. Â Even in a client/server architecture, I separate out the business logic so even though technically the business logic is compiled into the client, internally it is still acting as though it were a separate tier...
Since sub is using .Net, a better solution (although more work ) would be to abstract all database access into a separate assembly. Â Then he could publish the API and we could implement a MS SQL Server assembly in it's place... or any other database...
Technically, with this solution, the database wouldn't even have to have the same tables or names!
-Charles