DoCmd.RunSQL vs. Recordsets
Try:
CurrentDB.Execute (SQL statement as string)
Its faster than both docmd.runsql and recordsets.
Two tips:
(1) Your SQL table must have a primary key in order to update it via ODBC
(2) You must use the dbSeeChanges option in the Execute statement above.
Phil J
MCP
Quote:
> Just wondering... I used to do most operations from my Access client
> involving even simple data updates on the SQL server backend with
> recordsets. But somehow, RunSQL looks a lot easier in many situations. Is
> there any guideline or 'best practice' when to use one and when the other?
> Andrea
