Re: Which is best - recordsets/VBA V SQL statements for updating data

That is what I mean. A permanent table, in a separate back-end file, that
holds data temporarily. For same reasons as mentioned and where there is a
lot of processing that depends on the result of previous processing etc.

A pain in the *** necessary sometimes.

Jeff

"Bri" <not@xxxxxxxx> wrote in message news:Uszuf.127773$2k.11652@xxxxxxxxxxx
>
> 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
>


.

Quantcast