Re: Which is best - recordsets/VBA V SQL statements for updating data
- From: Bri <not@xxxxxxxx>
- Date: Tue, 03 Jan 2006 18:34:28 GMT
Lyle Fairfield wrote:
As you use SQL more and more, you will find fewer and fewer good reasons to use Recordsets.
Agreed!
Temp Tables! EWWWWWWWWW!
There are times that they are the only way to do a task and in those cases I use them. As a last resort. After I've tried every other thing I can think of.
Mind you, my definition of a temp table might not be the same as yours. To me a temp table is a permanent table that holds data temporarily. An example would be a POS product selection screen where the selection of products and quantities are all entered (into the temp table) and checked and payment is verified before the records are moved to the Billing table.
-- Bri
.
- Follow-Ups:
- References:
- Which is best - recordsets/VBA V SQL statements for updating data
- From: Jeff
- Re: Which is best - recordsets/VBA V SQL statements for updating data
- From: Lyle Fairfield
- Re: Which is best - recordsets/VBA V SQL statements for updating data
- From: Jeff
- Re: Which is best - recordsets/VBA V SQL statements for updating data
- From: Lyle Fairfield
- Which is best - recordsets/VBA V SQL statements for updating data
- Prev by Date: Re: Validating "Orders" form
- Next by Date: Re: Access to Quickbooks
- Previous by thread: Re: Which is best - recordsets/VBA V SQL statements for updating data
- Next by thread: Re: Which is best - recordsets/VBA V SQL statements for updating data
- Index(es):
Relevant Pages
|