Sorry i forgot to finsih my thought... What is the best way to replace them. slack

I have done my fair share of DB programming during the last years and all I have to say is... Stay away from ADO, it contains so many gotchas that it's plain silly. Also it really lacks the performance needed for heavy multi-user system. My recomendation would be OLEDB by using the ATL supportclasses (CCommand, CRowset and so on). Use the wizard to get the hang of things then write your own code by hand since the wizard (IMHO) is a bit to stupid to be used in production code. If you still REALLY want to use ADO get the MS Press book, Programming ADO (it's good), and read it cover-cover atleast 2 times then check out OLEDB again :)

Same for me :( WE NEED A SERVICE PACK !

Yikes!!!!!!! For a moment I thought I was in the wrong web site :-) Nish Sonork ID 100.9786 voidmain www.busterboy.org If you don't find me on CP, I'll be at Bob's HungOut

> If they're classes, with virtual functions [...]    Or even structures with virtual functions... > If it's just data, then no problem    You do, of course, need to be smart enough to consider alignment and packing issues (and sometimes endian-ness!) when dealing with reading and writing data structures in such a way.    Peace! -=- James.

You have to embed an interpreter in your program. There are plenty out there that are free and can be integrated into a C++ program. http://www.lua.org/ Todd Smith