DoCmn.RunSQL versus CurrentDb.Execute

Hello,



Is there any particular reason I would choose to use



DoCmd.RunSQL "insert into...



Versus



CurrentDb.Execute "insert into.... ??



I am using an unbound form on the front end of my database to populate the backend tables (multiple tables). Some forms only have a few fields, while other forms have about 15 fields with 3-4 tables updating.



I am okay using the DoCmn.RunSQL , but I keeping reading on the forum that others chose CurrentDB.Execute and it has me thinking.



My database is stored on a network drive with only on front end.



Thanks

Brent

DoCmn.RunSQL versus CurrentDb.Execute