I recommend not using DAO, but going with ADO. It is relatively easy to
implement and fast enough for most applications.
--
Michael D. Long
"Questioner" <james_pannozzi_at_cisgi.com> wrote in message
news:11a3fa8.0409090822.339ee514_at_posting.google.com...
> nospam1978_at_yahoo.com (Tom Barnes) wrote in message
> news:<5af28966.0409082039.66912151_at_posting.google.com>...
>> james_pannozzi_at_cisgi.com (Questioner) wrote in message
>> news:<11a3fa8.0409081010.6c05883b_at_posting.google.com>...
>> > I will read that Oracle Concepts Manual that was suggested
>> > and try to get more specific knowledge of Oracle options and
>> > capabilities.
>> >
>> > It almost seems like I would be better off retaining the C++ user
>> > interface and just communicating with Oracle from the C++ app
>> > somehow
>>
>> Yes, I agree. In the future try to separate your application's
>> presentation (user interface) from its model (data). Search for MVC
>> (Model View Controller) on google.
>>
>> > (or else using a C++ class, if one exists, that knows how to save in
>> > Oracle format, to save the records into the database)
>>
>> Go to otn.oracle.com and search for OLE.
>>
>> > but I will be surer once reading is done.
>>
>> In addition to reading the Oracle Concepts Manual I recommend you go
>> to a bookstore and check out any of the Oracle beginner's books. Also
>> take a look at some Visual C++ beginner's books (eg Ivor Horton's
>> books). They usually have a chapter on how to access databases through
>> ADO/DAO/OLE.
>>
>> Good luck.
>
>
> Thanks!
>
> I've used both DAO and OLE in the past but will reserve judgement on
> employing any of these until I know more about Oracle.
>
> Jim
Received on Tue Sep 14 2004 - 21:20:55 CDT
