append query how many records where affected

I am running this append query

CurrentDb.Execute "AppendToTable1", dbFailOnError

How would i determine how many records where affected.
vbnetcoderAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Dim X as Long


With CurrentDB

     .Execute "AppendToTable1", dbFailOnError
     X= .RecordsAffected
      Debug.Print X
End With
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Of course you can do anything you want with X ... display it in a Text Box, and so on.
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
You will also want to add some error trapping in case an error occurs with the Execute operation ... since you have dbFailOnError (good)
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Here is a full example more or lessv


Public Function mFx()
On Error Goto mFx_Error:

Dim x as Long  ' optional
With CurrentDb
      .Execute "YourActionQueryName", dbFailOnError '
       ' x = .RecordsAffected   'returns the number of records processed by the action query ' optional
End With

mFx_Exit:
   Err.Clear
   ' other clean up here
   Exit Function
mFx_Error:

   ' error trap code here
   GoTo mFx_Exit

End Function

Don't forget the Dots ....
0
aikimarkCommented:
I prefer a different database object.  It is a bit faster -- less overhead.
DbEngine(0)(0).Execute "AppendToTable1", dbFailOnError
debug.print DbEngine(0)(0).RecordsAffected

Open in new window

0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Good luck measuring the speed difference with today's faster systems :-)
In theory, yes a tad faster.
I stayed with CurrentDB because that's what the OP was familiar with ... and the real question was how to use RecordsAffected ...
0
vbnetcoderAuthor Commented:
ty
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.