DataBase development with Visual C++

[hargis]

Can anyone recommend any products to use for front-end database development with Visual C++?
I'd looked at several ActiveX controls but they were too buggy, too difficult to use, and poorly documented.
I've heard Rouge Wave has a DataBase class library and a MFC based class library but don't know if it'll be useful for what I'm doing.
What I want to be able to do is retrieve data, display it for the user as rows and columns or as a form, allow them to update, add, etc and update the database.
Really what I’d like is something like PowerBuilders DataWindow.
Any suggestions would be appreciated.

[Masaaki]

Hi.

While I took TCP/IP class, I did Socket porgram assignment by VC++ -
Actually, this is Unix stuff.
During this break, I updated Server side - connect to Access Database.
For example, Access databse consists three tables.
Customers, Balance and Transaction - simple ones.

If the customer enters Account # and password, Server check these
from Customer table. After customer enter amount, Transaction table
will be updated and Balance table will be done.

I use CDaoRecordset on runtime by using new operator and therefore,
the program can read three different tables at runtime.
close -> m_strFilter -> open.

But this has a potential problem - scurity - needed encryption program
and Access database performace.

The other approach is Java - RMI and JDBC-ODBC brige or JDBC
Client can use both stand alone application and applet.
Or ASP and SQL Server or Oracle.

Hope for help.
-Masaaki Onishi-

[ksheeraj]

You have several approaches to design your desired produt.
1.DAO engine :This is native engine to access MS-Access database.You can you it with the help of CDaoDatabase classes or directly through COM interface of DAO engine.
2.You can use ADO as a com object.
3.you can use RDO as a com object.
4.You can use ODBC API calls.
5.you can use OLDDB 2.0 Lib.
Hope this will help
Ksheeraj

39639,Leslie St.
Apt #157
Fremont USA 94538

[Marco]

I'm using ODBC and CRecordsets, 'cause they are most "flexible" for other database-formats and works best with SQl-Servers.

CDaoRecordsets and DAO 've got more functionallity than ODBC but You have to route everything through an Access-Database.