Leyusha wrote: 1- people tell me to go to visual basic to do it easily i want to use vc Don't allow others to dictate what tool(s) you use. Each person uses a programming tool for their own reason(s) and those reason(s) are heavily biased. I much prefer to use VC++ over VB, but I'm also smart enough to know that any judgment I have against VB can likely be countered by any VB aficionado. Unless you happen to stumble upon a person that is an expert in both languages, a fair comparison is much like dust in the wind. Leyusha wrote: 2- there are ADO,ODBC and stuff which one should i use ? Each is a tool designed for a specific purpose. While they do overlap to a small degree, it all depends on the intended application as to which is better suited for the job. Often times more than one can be used with no noticeable differences. ODBC gives you access too hundreds of 16-bit ODBC data sources. ADO also gives you access too hundreds of ODBC data sources but using a 32-bit OLE DB interface instead. DAO has both 16 and 32-bit support and is native for Jet and ISAM databases. Per MSDN: ADO has one common yet extensible programming model for accessing data—thus eliminating the need to choose between DAO and RDO and all of the others. ADO is not a specific “implementation” of a data access interface like RDO or DAO but a programming model. It implements a common programming model against OLE DB. DAO is an object interface that can be used to access ISAM (and ODBC) functionality using DAO/Jet or the remote RDO functionality using DAO/ODBCDirect. DAO is fairly easy to code and provides a rich set of cursors and cursor-less resultsets as well as DDL functionality. ODBC is a recognized standard interface to a variety of relational data sources. It is fast and lightweight and provides a universal interface that is not optimized for any specific data source. OLE DB is a low-level interface designed to be used by driver vendors that wish to expose a data source to ADO-aware applications or by C++ developers wishing to develop custom data components. OLE DB is not callable from Visual Basic as it is not COM automation-compatible.
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow