Before spending to much time with the wrong library, here are two scenarios where you're really not going to love DDO.

If you've got 5,6 or 7 tables in your database but 2,3 or 10 Millions of records and your application is presenting 10,000 record in a list view – don't start laughing I've seen such an application even built with REALbasic last year – then the DDO might be a showstopper, especially when you need to squeeze out the last 2% of performance.

The same for this nice paper management tool with 3 tables, 6 columns and in total 120 records where the DDO might be an overkill.

But if you wether going to design this mammut application nor this small tool, but the common business application, that you should read on.

Does your design depend on many different tables and a lot of joins between, perhaps organized in a complex tree and you tend to traverse the tree more than to search hugh result sets, then the DDO is the library you're looking for doing your job with REALBasic.

The mapping of your classes and the data structure, the object-relational-mapping (ORM) is the core function of the Dynamic Data Objects.

step 1: Describe your structure and the relation to your classes using simple XML-files.

step 2: Inherit your (data-)classes from DDOBasicDataObject or any inherited class.

step 3: there is no step 3 – use the objects in your application