Drew Wutka
DWUTKA at marlow.com
Sun Sep 21 22:54:53 CDT 2003
Actually, I personally use ADO when in VB, or any other system other then Access 97's VBA. The only time I ever use DAO is if I need a specific capability only native to DAO. On top of that, when I use ADO, I use Microsoft.Jet.OLEDB.4.0 for the provider. There was a bug in the 3.51 jet provider, which caused me a lot of extra work, which was fixed by just using the 4.0 drive. Thus, if you just use that driver in all of your VB code, you can alternate 97 and 2k mdb's with no changes whatsoever. (Even XP .mdb's, I think) Drew -----Original Message----- From: dave sharpe [mailto:davesharpe2 at cox.net] Sent: Saturday, September 20, 2003 10:40 AM To: Access Developers discussion and problem solving Subject: [AccessD] A97 MDB to A2k MDB- I use VB6 as 'Front End' ? I developed a small Package for our in office 'Company Store'. It is cheap & dirty cash register and inventory system a fw years ago. It isn't anything I'm real proud of, but It meets my user's needs. It is a VB EXE with A97 mdb. I'd like to convert the MDB to A2k and not touch the EXE. I expect to be able to just pull the ADO and include DAO in the VB project. Any guidance as to anything else to expect ? Thanks Dave _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com