Copy record omitting contents of combo box

[Kathy Webster]

I'm having trouble copying a record in a continuous form.
All fields are copying properly, EXCEPT the combo box field that is bound to
column 2.
All other fields, including the other combo box fields that are in the
record are copying fine,
since they are bound to column 1.

This used to work fine in Access97. My users pointed out the change in
functionality to me since we changed to AccessXP.

Help!
TIA,
Kathy

 

[Jeff Boyce]

Kathy

By "copying", do you mean reproducing what you see in the form, or what is
actually stored in the table?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Kathy Webster]

It's a form bound to a table; all fields are actual data stored in a table.

 

[Jeff Boyce]

Kathy

So, you are saying that you have data in one table, and, via your form, you
are copying the same data into another table?

By the way, if the field underlying that combo box is defined as a "lookup
datatype field", you might be running into the difference between what is
stored and what is displayed.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Kathy Webster]

No. The users are copying a record from a table, via the form, and pasting
the same record to the same table in the same form. Why, you may ask? So
that they can just change one field in the new record. It is a record
containing an event, description, party_name and date. When a new entry
needs to be created for the same event, description and party name, but
simply a different date, rather than re-enter everything, the users have
historically (historically meaning with Access 97) copied the original
record, then pasted the original record, and simply changed the date on the
new record. Now, with Access XP, when they try that, all fields copy EXCEPT
the partyname field, which is a combo box.

 

[Jeff Boyce]

Kathy

Did you check the underlying table/field definition to see if a lookup field
is being used? What is the code behind the combo box's row source?

One approach might be to add a command button that inserts a duplicate (same
field values) record, then changes the date.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Kathy Webster]

I found the error. It was my mistake. I had the default value of that
recordID field set to zero, instead of null. Once I changed it to null,
everything worked fine.
Kathy