MDI or SDI for an Object-Oriented Database?
pclark@Incite.com
Wednesday, April 10, 1996
Hello All
I'm looking for some suggestions on implementing a MFC interface to an
object-oriented database, Objectivity's database to be exact. I'm trying to
decide to make the entire DB a document (SDI), or certain objects and there
associations a document (MDI).
System : P-90
Windows NT 3.51 Service Pack 4
Visual C++ 4.1
Any suggestions will be appreciated.
Paul Clark
INCITE "Where LAN's Come Alive"
214-447-9000
pclark@incite.com
URL http://www.incite.com
Mike Blaszczak -- mikeblas@msn.com
Saturday, April 13, 1996
----------
From: owner-mfc-l@netcom.com on behalf of pclark@Incite.com
Sent: Wednesday, April 10, 1996 7:12 AM
> I'm looking for some suggestions on implementing a MFC interface to an
> object-oriented database, Objectivity's database to be exact. I'm trying to
> decide to make the entire DB a document (SDI), or certain objects and there
> associations a document (MDI).
In my experience, the user interface of a database application is tied far
more closely to the data being managed than any physical aspect of the storage
mechanism. You should decide how to design the user interface of your
application based on the way your users would like to see the data, not on the
way your storage mechanism is implemented.
.B ekiM
TCHAR sz[] = _T("I don't speak for Microsoft.");
Graham Stalker-Wilde -- GSTALKER@CSFBG.CSFB.COM
Tuesday, April 16, 1996
>> I'm looking for some suggestions on implementing a MFC interface to an
>> object-oriented database, Objectivity's database to be exact. I'm trying
to
>> decide to make the entire DB a document (SDI), or certain objects and
there
>> associations a document (MDI).
>> From: pclark@Incite.com
>In my experience, the user interface of a database application is tied far
>more closely to the data being managed than any physical aspect of the
storage
>mechanism. You should decide how to design the user interface of your
>application based on the way your users would like to see the data, not on
the
>way your storage mechanism is implemented.
>.B ekiM
Basically I agree with Mike that the representation of the data
should not be linked to the database structure.
You should aim to be able to replace your DB (with ODBC, DAO,
proprietary, flat file, whatever) and not touch the GUI code.
OO Databases are nice from an implementation point of view,
(you don't need 300 CRecordSet classes to get anything done;)
but they're still Computer Science constructs. Users are interested
in data, not databases.
| Вернуться в корень Архива
|