SQL vs Recordsets for unbound operations

[NXMold]

I am setting up a purchase order system and have decided to add new records using VBA, and also deleting them if certain conditions are not met.

I started to implement this with docmd.runsql and warnings turned off, but now I wonder if its better to use recordsets, particularly in case of an error.

Any comments on the reletive merits of each approach?

 

[Remou]

I like Execute best.

Set db=CurrentDB

db.Execute strSQL, dbFailOnerror

lngRecords=db.RecordsAffected

Or

    Set db = CurrentDb

    Set qdf = db.CreateQueryDef("", SQLText)
    qdf.Parameters!txtEvent = Trim(frm!txtEvent)
    qdf.Parameters!dteCRDate = Now()
    
    qdf.ReturnsRecords = False
    
    qdf.Execute dbFailOnError
    
    intResult = qdf.RecordsAffected

http://lessthandot.com

 

[NXMold]

I was unaware of that method, thanks.

 

[TheAceMan1]

How are ya NXMold . . .

The best and the fastest methood for adding new records is a [blue]bound form![/blue] Why is this not a consideration? ... it would certainly circumvent having to generate the code that access already does for you!

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[JoeAtWork]

Or if you like doing it with ADO:

CurrentProject.Connection.Execute "DELETE * FROM MyTable"