Re: Normalizing Question

Tech-Archive recommends: Fix windows errors by optimizing your registry

Great comment. I haven't heard the term "bucket table" before but have used
them for time*** entry to display a week's worth of work time.
--
Duane Hookom
MS Access MVP

"Craig Alexander Morrison" <cam@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:u2FN1qNcGHA.536@xxxxxxxxxxxxxxxxxxxxxxx
Duane whilst not wishing to encourage unnormalised data I would suggest
that
rather than an unbound form you could have a "bucket" table that collects
the data from the form and then via a series of Queries transpose the data
from the "bucket" to the proper central database tables.

This can be done in both directions using a series of Queries to move the
data into the "bucket" table for display on the form and then using a
series
of Queries to move the data from the "bucket" and clear it out ready for
the
next use.

The bucket table would be best implemented in the application to allow
different users to have their own buckets and to keep it away from the
pure
relational database which may be offended having such a abomination
imposed
upon it. (g)

The risk with both approaches (unbound and "bucket" bound) is that users
working on the same data will not be as aware of each others updates as
they
would be if they were working on the live central database data.

(vbg) start
This approach is recommended for users who have
more money than sense,
after they pay for the development they may have
more sense than money.
(vbg) end

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited


"Duane Hookom" <DuaneAtNoSpanHookomDotNet> wrote in message
news:eXFhp6LcGHA.4604@xxxxxxxxxxxxxxxxxxxxxxx
My solution has a continuous subform which provides multiple text boxes.
I
guess if you can't get users to enter data in that style of form, my next
step would be to create a large unbound form with a grid of text boxes.
It
would take a fair amount of code to fill the text boxes from a recordset
and then push the values back out to normalized tables when finished
entering.
--
Duane Hookom
MS Access MVP

"RMires" <RMires@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:32ACDA2D-B64F-4C0B-A1AD-5413A0F5DEE5@xxxxxxxxxxxxxxxx
I think this gets down to the crux of the problem I've had reguarding
every
step of this database. I would like to end up with a form that has a
textbox
for EVERY gauge. This may be problematic for the database but would make







.

Quantcast