Turn off Auto Fill In???

[Doug in Texas]

Running ACCESS 2000 on XP home.
I have a query I run to select a group of records to print a set of product
labels. I go through the selected records in the Datasheet view to enter a
quantity (qty) of labels I need for each record (1, 2, 3 etc) I skip some
records and enter a qty in other.

If I enter a sequence of numbers in 2 or more consecutive records, I get an
auto fill that enters the next records number in the sequence automatically.

This would be fine if I watched the entry each time, and it is easy to
delete the auto filled entry, but I key the numbers without watching the
column as I look at my invoice. If I miss one of the auto fills I get lables
I don't need.

Example:
I enter 2 in qty for record 3
I enter 4 in qty for record 4
I get an autofill in qty of 6 for record 5
I want to shut off the auto fill of the next entry? Can someone help?

Thanks,
DougInTexas

 

[John Vinson]

If I enter a sequence of numbers in 2 or more consecutive records, I get an
auto fill that enters the next records number in the sequence automatically.

This is a VERY annoying misfeature introduced in Access2000 by someone
who mistakenly thought that Access tables should work like Excel
spreadsheets.

There's no way to turn it off; but what you can do is base a continous
Form on the table (or on a query based on the table). A continuous
Form doesn't have this obnoxious behavior but will let you update the
data.

John W. Vinson[MVP]

 

[Doug in Texas]

This is a VERY annoying misfeature introduced in Access2000 by someone
who mistakenly thought that Access tables should work like Excel
spreadsheets.

There's no way to turn it off; but what you can do is base a continous
Form on the table (or on a query based on the table). A continuous
Form doesn't have this obnoxious behavior but will let you update the
data.

John W. Vinson[MVP]

It would be a useful feature in some circumstances, but for my purposes,
it's become a bothersome nusance. Thanks for the work-around.

DougInTexas

 

[Allen Browne]

Doug, this might not be much help for you now, but Microsoft has heard this
pain point and removed this annoying behavior from Access 2007.

In the meantime, John's workaround is what I use too.