Is there a comparison or am I talking apples and oranges? Here's where I sit. I have a VB6 front end that uses ADO to retrieve a recordset from an Access 2000 database. I modify that recordset, the do recordset.update to put it back to the Access table. So far, so good.
Within this Access database I have some VBA code that manipulates the tables (updates, new tables created, etc.) and then VBA code that exports those table to text files. I currently use a 32 bit Shell program to open the Access database. The database has a form that loads automatically. That form has the launch codes for the VBA modules in the database. I work with the text files then relaunch the Access database in the Shell. The form knows I'm coming back the second time, and launches the module to pull those text files back into new tables.
Im thinking there is a better way. I need to manipulate the tables (which I know I can do through ADO). But COM exposes Access functionality and I need it, I think, to do my import/export to text files. COM would give me this.
So is there a best way to do these types of things? ADO or COM? Thanks.
Within this Access database I have some VBA code that manipulates the tables (updates, new tables created, etc.) and then VBA code that exports those table to text files. I currently use a 32 bit Shell program to open the Access database. The database has a form that loads automatically. That form has the launch codes for the VBA modules in the database. I work with the text files then relaunch the Access database in the Shell. The form knows I'm coming back the second time, and launches the module to pull those text files back into new tables.
Im thinking there is a better way. I need to manipulate the tables (which I know I can do through ADO). But COM exposes Access functionality and I need it, I think, to do my import/export to text files. COM would give me this.
So is there a best way to do these types of things? ADO or COM? Thanks.