Parts Database; Updating...

  • Thread starter Thread starter Tim Fierro
  • Start date Start date
T

Tim Fierro

Hello, I have a couple of questions I hope someone can answer for me.

I wrote a database for our parts room and we have been using for the past
few months; all is well. However, since that time, I have found a few
things I want to adjust/add/fix etc... One of these is to create a field in
a few tables for a POSTED DATE field.

tblInvoice, tbleOrder, tblLabor

1) What is the best way to add a new field (invDatePosted, ordDatePosted, &
laborDatePosted) to 3 existing tables? I want to insure that I also fill
these new fields with a date of "12/31/2004" as a starting point. I am also
going to set these fields to required.

Should I use some kind of query to make this update? Suggestion(s)?

2) When adding a new field to table(s), is there any issues I should be wary
of? Such as forms that want this new field displayed will need to be
adjusted, but those forms that don't care about this field, they are fine as
is?

I was just wondering as I have never added fields after the fact before and
this will be an update for me. These fields were not thought of during the
design and creation phase.

Thank you for any help or suggestions you post,


Tim
 
Tim said:
Hello, I have a couple of questions I hope someone can answer for me.

I wrote a database for our parts room and we have been using for the past
few months; all is well. However, since that time, I have found a few
things I want to adjust/add/fix etc... One of these is to create a field in
a few tables for a POSTED DATE field.

tblInvoice, tbleOrder, tblLabor

1) What is the best way to add a new field (invDatePosted, ordDatePosted, &
laborDatePosted) to 3 existing tables? I want to insure that I also fill
these new fields with a date of "12/31/2004" as a starting point. I am also
going to set these fields to required.

Should I use some kind of query to make this update? Suggestion(s)?
Click to expand...

That's what I'd do. First, add the 3 fields. Second, run an Update
Query that stores #12/31/2004# into each of these fields in all of the
records. Third, change the field properties for each field to "Required".
2) When adding a new field to table(s), is there any issues I should be wary
of? Such as forms that want this new field displayed will need to be
adjusted, but those forms that don't care about this field, they are fine as
is?
Click to expand...

Forms that make no use of the new fields should not be affected.
I was just wondering as I have never added fields after the fact before and
this will be an update for me. These fields were not thought of during the
design and creation phase.
Click to expand...

Access is intended to be somewhat flexible. If you wish, you can set a
Validation Rule (such as "is not null") for each of these fields. It's
possible that, if you don't set the initial values properly via the
Update Queries, you may get an error message when you try to impose the
new rules.

-- Vincent Johns <[email protected]>
Please feel free to quote anything I say here.
 
Back
Top