Use Access recordsource or DAO?

[ColeChaW]

Just wondering on the best practice for linking an Access form to the Access tables. There is the default link access creates directly to the tables in the database. To get at information you can also set up a DAO or ADO recordset and save the data to variables.

The second method seems safer because you can play around with the strPhoneCell and not mess up the data stored in PhoneCell in your table. Then, when they save the data, you can just replace the data using you DAO.

However, I'm not sure if this is overkill, using it on every form or if there's a general rule out there. I'm a paramedic by trade, so I might be overlooking some very general development issues here. If something doesn't work right at my job we just shock it.

Also, the dcount dlookup ect. commands are real good at getting info quick, should I use a DAO connect for this info too or are the 'd' commands a good way to get a quick single peice of information?

Thanks for sharing your brains.

 

[dsigner]

An Access form has a record source. This is either a single table or a query if the data comes from more than one table. This will work for many requirements and is the easiest solution because Access looks after the data for you. Only use Recordsets where the simple way is not doing what you want it to.

 

[ColeChaW]

Thanks. I'll keep on using the Access forms where I can get away with it.

 

[Pat Hartman]

Access is a rapid application development tool. If you don't use bound forms, you are tying both hands behind your back and trying to press the keys with your nose. If you understand how form events work, you have as much control with a bound form as you would have with an unbound form for a fraction of the work.