[AccessD] lock data2

In that case I think you have to store the cost in the order table and only
write to that field on a new record.

Could you add the table and the relationship?

Reuben Cummings
GFC, LLC
phone: 812.523.1017
email: reuben at gfconsultants.com


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Pedro Janssen
Sent: Tuesday, May 03, 2005 4:25 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] lock data2


Reuben,

thanks for your help, but the structure of the database isn't build for a
price history, by adding a new record.
For us that isn't what we are looking for.

Pedro Janssen



----- Original Message -----
From: "Reuben Cummings" <reuben at gfconsultants.com>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Friday, April 29, 2005 5:37 AM
Subject: RE: [AccessD] lock data2


> I have to concern myself with similar issues.
>
> I do this by adding a new record with the new amount and the effective
date
> (in a one-to-many table) rather than overwriting a single record.
> Essentially you will be building a price history for an item.  You will
then
> use the order date to set the price according to the order date when
opening
> the order each time.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Pedro Janssen
> Sent: Thursday, April 28, 2005 4:01 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] lock data2
>
>
> Hi,
>
> this problem was badly explained, so i will try again.
>
> I have a table in which data about bricks and their prices are stored.
> I use this data in a form where the orders of these bricks are stored. The
> prices of the bricks are used only as lookup (the price can't be changed
by
> hand on this form).
> The prices in this form are used to make bills by mail merge with word.
> When the price of a brick (for example A)  changes and the price in the
> table for brick A is will be changed to.
> When opening the order form and changing other data in the order for brick
A
> the original price will be updated with the new price.
> How can i prevent this. When i place a order, the price at the date of the
> order must stay on the form, even when the price of this brick is changed
in
> the table.
>
> Pedro Janssen
>
> ----- Original Message -----
> From: "Pedro Janssen" <pedro at plex.nl>
> To: <AccessD at databaseadvisors.com>
> Sent: Thursday, April 28, 2005 2:21 PM
> Subject: [AccessD] lock data
>
>
> > Hello Group,
> >
> > i have a form that is using a table to store its data of stone prices.
> When the prices in the table changes, the data on the form also changes.
> >
> > I would like that the prices can not change, after it is places on the
> form the first time, when the record is opened.
> >
> > TIA
> >
> > Pedro Janssen
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> >
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com