[AccessD] Data interface The best way

Jim Lawrence accessd at shaw.ca
Wed Oct 19 19:13:10 CDT 2005


Ken this is a very interesting subject.... and warrants further research.
Though it is not immediately relatable to the current versions of Access, I
will not be surprised when these model variants start to morph 'our'
database. 

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Ken Ismert
Sent: Wednesday, October 19, 2005 12:26 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Data interface The best way


Shamil,

>As for "an object design down to the lowest level" - 
>this is still questionable here how it should be done - 
>and it's getting the more questionable what this design 
>should be the more I'm getting into the modern methods 
>of OOP&D... 

Theoretical questions aside, the notable object-data systems doing
useful things now are the open-source web frameworks using the
Model-View-Controller model. Ruby on Rails is the prime example.

Since I have far from a deep understanding of MVC, I will just point out
that the data objects are modeled in code, and changes in the data
objects are reflected to the table structure of the underlying database.


One challenge that future OO DBMS projects will have is equalling or
bettering the ease-of-use of these MVC frameworks. One thing is certain:
they'll never beat the price.

Ruby on Rails
http://www.rubyonrails.org/

Django
http://www.djangoproject.com/

TurboGears
http://www.turbogears.org/

Ruby on Rails
Model-View-Controller Article
http://en.wikipedia.org/wiki/Ruby_On_Rails

-Ken
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list