Recordsets vs. Linking Recordsources to Tables or Queries

[dgunner71]

All,

I have created several MS Access databases over the last 11 years that have worked very well but I have always set forms to link directly to either a table or query. While this seems efficient, it can cause issues or corruptions in a record being edited when the front end and back end are located on separate machines and there is an interruption in the network.

I have long considered using Recordsets and a save command to load data / update records. It looks like a lot of coding but a good option - A few questions:

1.) Can you please tell me any pros and cons of Recordsets as compared to just linking to an underlying table/query.
2.) Are there any locks / limitations / memory concerns / trade offs / pitfalls / etc. when using Recordsets?
3.) Is one way or the other considered to be the standard / best / most professional route?

As always, thanks for your direction!

Gunner

[NeoPa]

1. Recordsets bypass all the help that Access gives for using bound Forms/Reports.
2. Locks are configurable, but ignoring locks is a minefield in itself. Otherwise access to the data is required which ever way you approach it.
3. Bound objects is the standard approach. It's what Access was designed to do. That's not to say there aren't reasons to do it differently sometimes, just what it says. Bound objects is the standard and most common approach.

[dgunner71]

Thank you NeoPa. I think I was really looking for the answer in #3 (best practices).

Happy holidays!

[NeoPa]

Always happy to help my military friend :-)

[dgunner71]

Hoo-rah!

Happy holidays.

[NeoPa]

You too my friend. Stay lucky!