K
kagard
Greetings:
I created a table with three fields: an autonumber, an integer, and a
date/time field. I set no validation rules or default values. When I
save the table and start entering data in datasheet view, it acts
strangely. If I put 2 in the integer field and press the tab key,
access puts 3 in the date field and then throws an error saying the
data is invalid. If I put a 3 in the integer field and press tab,
access puts 5 in the date field and throws the invalid data error
again. No other numbers that I've tried cause access to fill the data
field with a value. I've reproduced this behavior from scratch with a
second table. I've also compacted and repaired the db on the off
chance that access was getting confused. (I'm using Access 2002.)
This isn't a critical problem, so I'm not concerned if I get an
answer. I thought, though, that some of you might find this curious.
Anyone else encounter this anomaly? Any idea what's going on?
TIA
Keith
I created a table with three fields: an autonumber, an integer, and a
date/time field. I set no validation rules or default values. When I
save the table and start entering data in datasheet view, it acts
strangely. If I put 2 in the integer field and press the tab key,
access puts 3 in the date field and then throws an error saying the
data is invalid. If I put a 3 in the integer field and press tab,
access puts 5 in the date field and throws the invalid data error
again. No other numbers that I've tried cause access to fill the data
field with a value. I've reproduced this behavior from scratch with a
second table. I've also compacted and repaired the db on the off
chance that access was getting confused. (I'm using Access 2002.)
This isn't a critical problem, so I'm not concerned if I get an
answer. I thought, though, that some of you might find this curious.
Anyone else encounter this anomaly? Any idea what's going on?
TIA
Keith