Darsant Silverstring
darsant at gmail.com
Sat May 7 15:21:08 CDT 2005
Unfortunately right now the application they are wanting to connect to is in Visual C. I'd like to use insert statements but it goes against the standardization of what they have in their coding at the moment. In the future I can probably convert it over to an SQL statement, but it'll take more work than they want to commit to standardize and escape the correct characters in the SQL string. I'm going to try the Top 1 query and see how that does at reducing cpu time. At the moment it's running about 48hrs for about 1.5GBs of Access databases. As someone else brought up, is it possible to open a table-recordset from ADO and set it to append only? (Not sure if there's much difference on the ADO side from doing a select * query or just opening with table name). Thanks for everyone's help. Josh On 5/7/05, Stuart McLachlan <stuart at lexacorp.com.pg> wrote: > Don't bother to open a recordset at all (ADO or DAO). Just us Jet SQL. > > strSQL = "Insert into tblNames (LName,FName) values('Fred','Nurk')" > > CurrentDb.Execute strSQL > or > Docmd.RunSQL strSQL > > If you use SQL for all your data manipulation code, you don't even need a > reference to the ADO or DAO libraries in your mdb. > > > -- > Stuart > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- Darsant Silverstring "Peace cannot be kept by force. It can only be achieved by understanding." -Albert Einstein