Listing data in Combo Box from table and writing it to a new table

C

Curt Johnson

Wow it has been years since I have worked in Access. I am now creating a form
with many combo/ text boxes that will pull data from an existing table or
calculate some math calculations. I have got all of the calculations to work
etc, and now I want to store these completed values into a new/different
table. I am drawing a blank on how to write the values to a new table.Can
someone please help me???
 
L

Larry Daugherty

Yes, Don't Do It!

Instead, recalculate each time you need the results.

It's against the relational rules to store values in a database that
are the result of calculations on other values in the database.

HTH
 
C

Curt Johnson

Thanks Larry - But I still need to capture the calculations in those fields
and write the values to a new talbe for pricing reference later. Let me give
you a better explaination. We have a very complicated formula ( which is
imbeded in the form I have created) for the products that we make. I have
created tables that supply -ex: resin, pigments, additives, and or
lubricants, with pricing for each product. I will need to update each table
with the constantly changing pricing which will change the overall price for
the thousands of products that we supply. I will use this data to create
price lists for our customers. Can you write some code that will take the
data from many text boxes and place it in a table or have TEXTBOXa= TEXTBOXb
( where textbox A is bound to the resin table and textboxb is bound to the
newpricing table?? Hopefully I have explained this clearly.
Thanks for all of your help.
Curt
 
L

Larry Daugherty

Hi Curt,

Your explanation was pretty clear

My suggestion would be to move those calculations out to the Reports
you'll use to generate the price lists for your users. You can even
call function procedures from your Report's query to execute some
pretty complex calculations. Just put your heavy calculations into
named function procedures in standard modules rather than form
modules.

It's very easy to do what you ask but storing the results of
calculations on other elements in your database is the wrong thing to
do. When Codd and Date were formulating the rules for relational
databases circa 1970 they weren't looking for ways to restrict the
software engineers" freedom nor to make them jump through hoops.

I'm trying to help you do things the right way. That being said,
there's nothing to stop you from seeking someone willing to help you
do things the way you want.

HTH
 
Top