One favour plz.

Dear Professional...
Can you plz tell me one thing like I have one XML file which is already
saved in C:\File1.xml path.
I want to parse that File1.xml file and save it into database through any
stored procedure or any command but the problem is that how can I call the
file File1.xml from the hard disk and parse it and save it into customer
table. I would highly appreciate if any one guide me this.
Thanks
NOOR
You may want to check out www.sqlxml.org
It has several short tips and guidelines on using the xml features with SQL
Server 2000. In your case, OPENXML function would be appropriate, the
details & examples of which can be found in SQL Server Books Online.
Anith

OLE DB or ADO? plz give me a suggestion!

i am learn database access with native vc++, so ADO.NET is not electable for me.

i wonder whether i should study OLE DB first or ADO.

i've been working with ADO under VB for some time, it's very simple to use. but i dont think it's the best choice for vc++, i think it's OLE DB. but OLE DB is really difficult, too many interfaces, and properties!!!
could u give a suggestion? should i learn ADO with vc++ first and then OLE DB, or sould i learn OLE DB directly?

I would not suggest using ADO, use OLE DB if you're trying to stay native (since ADO has been superceded by ADO.NET). You could also use the C libraries that many database vendors supply.

Is there a reason you're using native C++ database calls, and not something like ADO.NET? Just curious,

Josh Lindenmuth|||thank for your suggestion! i use native C++ because i like it, and i am a student, i am learning native VC++. ADO.NET is great, it does a lot for you. but i want to learn more about the system.

the biggest problem i am facing now is about the data conversion and binding, i can find much material about this subject on MSDN. and the Property Set too, almost every call need a set of properties, but no body tell why i need them. and it seems that many calls can work with NULL property set!!!

is there any nice book for teaching OLE DB?|||

I still say if you're going to use OLEDb, use it through ADO.NET (there's an OLEDB data provider). You'll develop code faster, and it will probably perform better as well. Otherwise, I don't see much use ... if you're going to use native C++ I'd still suggest using ODBC or one of the database specific C libraries that many vendors provide.

Here are two older books on the subject of ODBC and OLEDB:
http://www.amazon.com/gp/product/0764533088/102-6516636-3196933?v=glance&n=283155&v=glance

http://www.amazon.com/gp/product/1572316128/102-6516636-3196933?v=glance&n=283155&s=books&v=glance

Hope this helps,
Josh Lindenmuth

|||thanks!!
one more question!
if i want to code a lightweight COM component, should i use ATL+ODBC or ATL+OLE DB ?|||

You should also look at ODBC. It is a simpler API with fewer calls and hence is easier to learn than OLE DB. OLE DB would be a good choice if you plan to become a COM expert, otherwise ODBC may be your best bet. For most tasks you will write less code with ODBC than you would with OLE DB.

|||yes, i want to be a COM expert! but the OLE DB interfaces are really difficult for starters, however, ATL make it much easier to use! i think i can use those wrapped OLE DB interfaces first!