If there is that much common data, then there is a strong possibility that
redesigning the database according to good relational database design
principles could both reduce redundant storage and simplify your entry of
data (e.g., just use a foreign key to point to a related record that
containst the common data).
I think you may find something useful in the Microsoft sample databases,
Orders and Solutions, that you can download from
http://www.mvps.org/access/downloads/bapp2000.exe. Also the Orders and Order
Details tables in the sample Northwind.MDB that is installed with Access
(referenced, I think, in the Solutions sample) may indicate how it can be
done.
That said, if you must continue with your current design, create Form-level
variables for each of the fields of interest, save the value of the controls
into those variables in the BeforeUpdate event, and set the Controls from
the variables in OnCurrent, but only for a new record.
Larry Linson
Microsoft Access MVP
"Tom Cusick" <tj*****@yahoo.com> wrote in message
news:36**************************@posting.google.c om...
We have a Job Shop database. When I get an order in I put all the
line item information into the database. Some orders have multiple
lines and most of the information is the same. (eg. Customer Name, PO,
Due Date, Received, etc.)
2 questions:
1. I have a button to create a new record on my switchboard, but what
I would like that button to do is create a new record but enter in the
next job number. Our job numbers are 'H1001', so I would need the
button to search to the end of the DB find the last job number, add
one to it, and then plug it into the new record when it opens up.
2. After entering in all the info on to the first index, I want to
have a button that will open a new record but transfer all the
existing data (that is common) to the new record, but also increase
the index number. The Job number would be the same and would just be
a copy to the new record.
Does that make any sense?
Thanks,
Tom Cusick
