Append to changed

[Jennifer]

I had to reformat dates in some queries from 1/2008 to 01/2008. Since I did
this my append queries return error messages that say "The INSERT INTO
statement contains the following unknown field name: '1/2008'. Make sure you
have typed the name correctly, and try the operation again. When I go to
design view in the append query the append tos are wrong. The fields are
correct in saying 01/2008 but the append tos say 1/2008. However, if i go to
the drop down they have the correct 01/2008 options. I tried changing these
and then saving but when I open up design view again they are all changed
back to the 1/2008 format.

How do I fix this?

 

[Jeff Boyce]

Jennifer

Are you trying to append a date value? "1/2008" or "01/2008" are not date
values in Access.

The error message you're getting tells you that Access is attempting to
treat '1/2008' as if it were the name of a field.

Be aware that there is a BIG difference between how a (true) date/time value
is stored in an Access table, and how you can display it in a query or
report. Perhaps you want to display a true date/time value as "01/2008" ...
that's a different matter altogether!

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Jennifer]

I'm not appending a date value..I don't think. Here's what I'm trying to do.
I have different billing information for each month for different cost
centers. When I append the data to the master table it appends the following
fields:
Cost Center
SortOrder
Customer
01/2008
02/2008
03/2008 etc.
SUM

Does that answer your question?

 

[Jeff Boyce]

Jennifer

If '01/2008' is not a date, what is it?

Are you saying that you have fields named "01/2008" and "02/2008" and ...?
Are these fields into which you put something related to January, 2008, and
to February, 2008 and to ...?

If so, stop now! That design is exactly what you'd probably need to do ...
if you were limited to a spreadsheet! You won't get (easy) use of Access'
relationally-oriented features/functions if you feed it 'sheet data.

We're not there. We don't know the subject area like you do.

You've described a bit about "how" you are trying to do something.

If you'd like more specific suggestions, provide more specific descriptions
of "what" and "why" (the business need) instead of the "how".

Regard

Jeff Boyce
Microsoft Office/Access MVP