Auto populate fields

[kkramer]

I have a table in Access which is auto populating fields which I do not want to happen. If I list a number in a field, and then another number in the field below it, and then a third number, if those numbers happen to coincidentally follow a pattern (for example, 10322,10324,10326), the fields below are auto populating to follow the same pattern. I can't seem to figure out how to shut that off--it must have been a default because it wasn't purposely set it up that way. The whole table is set up that way.

It's Access 2003 that I am using, but the table itself was conceived in an earlier version some years ago.

I tried looking for how you DO set it up to do this, and then I would be able to undo it. But I have not had any success.

[JConsulting]

I have a table in Access which is auto populating fields which I do not want to happen. If I list a number in a field, and then another number in the field below it, and then a third number, if those numbers happen to coincidentally follow a pattern (for example, 10322,10324,10326), the fields below are auto populating to follow the same pattern. I can't seem to figure out how to shut that off--it must have been a default because it wasn't purposely set it up that way. The whole table is set up that way.

It's Access 2003 that I am using, but the table itself was conceived in an earlier version some years ago.

I tried looking for how you DO set it up to do this, and then I would be able to undo it. But I have not had any success.

1) if this is an autonumber, then this is an expected behavior
2) if it is NOT an autonumber, then check the default value in the field properties to see if there is any kind if incrementing code. If so, remove it?

Are you sure that this functionality isn't needed throughout your DB??

Make a backup before you do this.
J

[Scott Price]

This appears to be a 'helpful' feature of MS Access. I can reproduce it as well (using Access 2003). However, it only shows up when entering a patterned value, then down-arrowing to the next field in the same column. If you tab to another field, it won't show up, if you up-arrow, then return, it doesn't show up.

This all is a little aside from the main point, though, which is that you should strongly consider interacting with your data through a form, not directly with the table... You can build in more levels of data validation through forms than you can in a table. If this is a database that other people would be working on, then you should definitely not even consider letting others input data directly into the tables.

Regards,
Scott