[AccessD] A2K: BOUND to be a problem

Francisco H Tapia my.lists at verizon.net
Wed Mar 3 19:04:22 CST 2004


The most basic most elementry type of form in the world, and yet Access 
likes to give me a little curve ball :)

I have a form in datasheet view (yeah the boss likes the excel look), 
Now the table does not have an autonumber in this field, it's just a 
basic plain table bound to a form. NO query, no other special needs.

when adding text values to a particular field, when he begins coding 3 
lines in a row in this sequence

1 (down arrow) 2 (down arrow) the 3rd line automatically populates the 
field w/ the #3, now if he hits ESC it won't continue until he meets the 
same criteria as above, however if he continues simply pressing the down 
arrow the next row field increments by one, so, after 3, 4, 5, 6, 7... 
and so on.. But it doesn't seem to overwrite the previously populated 
fields... he has a unique coding structure for this field(column) such 
as 1, 2, 22, R, etc... there is no combobox because that's the way the 
boss likes it, but this problem cropped up in Access2000 because 
previously this was an Access97 form.(It upsized to Access2000.)

-- 
-Francisco





More information about the AccessD mailing list