I’m doing a database for Mark’s school. I’m doing the work in Access 2000 at the moment & when we enter any data into fields in table view, if it has a hint of a pattern, it adds a value in the next field eg 4 in one field, 5 in next, it auto-enters 6 in the next field in that record. Which is really annoying, particularly as many of the fields have a value no greater than 5 restriction set & it pops up an error message each time.
I’ve tried searching the help on autofill & autocorrect, autoentry etc and can’t find anything useful. Help me obi-teemingmillions-kenobi, you’re my only hope! I know that sounds flippant, but the rest of the post was fairly dull, so I thought I’d try to wake you up again. It’s driving me mad & microsoft help is being as helpful as usual…
No, they’re just set to Number. Autonumber increments down the field when a new record is added anyway. This is happening as data is being typed in running across the record.
Ok, having just been migrated to Access 2000, I went and took a look. I can’t replicate the problem you’re describing. Do you mean that if you’re typing a record, and you have a sequence of numbers in one field, that as you’re typing, it continues the sequence?..I’m afraid I can’t make my version do anything at all like that. Perhaps if you tell me what exactlly you’re doing.
Hmmm…wierd. It’s never happened with Access 97 to me before–I hope it’s not a bug with the 2000 version. I’m surprised it’s still producing numbers in fields at all if it’s not on AutoNumber.
Could you check to see if it still does the same thing when you enter fields in Data View? It’s worth a shot.
Perhaps also you could transpose two fields in Data View so that “test1,” “test2” and “test3” aren’t consecutive. Also worth a shot.
I’ll have to go away and think about this one…it does sound odd.
I first noticed this last night.
I was entering data directly in a table. Typed ‘3’ in one record and ‘4’ in the next, and it started auto-numbering. How obnoxious.
Are you using the table itself, or a form bound to the table? I haven’t noticed this when I’ve used a form.
David
Ok, finnaly replicated your problem. I was creating the fields as numbered instead of text. A quick way of getting rid of this problem, is to set the default value in design view to be “0” for each field. This will keep if from autofilling across a record. I’ll keep looking and see if I can find out what’s actually making it do this.
Thanks, Atrael, padabe, Duke. I’ll try the default 0 value option to at least avoid the stupid thing breaking data restrictions every 5 seconds. ALthough the fields were Number type, not Text type, but if it works, it works.
I’m glad someone else managed to get it to work (fail?). It isn’t listed at all in the help (unless they have converted it to Microsoftese, a language spoken by no human). It’s never happened to me in 97, I tried to get it to do the same mistake at work (Office 2000) & it wouldn’t. I can’t help wondering if there is a global auto-fill setting for Office 2000, so the setting isn’t contained in Access as they weave tehir applications closer & closer together (in the help file, they call them data sheets & sub-datasheets & pivot tables now, not TABLES! If I wanted Excel, I’d have used Excel…)
AutoNumber just assigns a unique number to a record in Access, contrary to my previous post. Why they ever hired me as a DBA here I’ll never know :rolleyes:
Atrael is correct: assigning 0 as a default number will solve your problem.
It’s not a bug, it’s a feature!
And a feature that you can’t disable, at that…
Knowledge Base article
Funny, they don’t bother telling you how you can get around it by specifying a default value.
Why does Access 2000 help suck so bad? Searching for “table” and “autofill” gets you squat. Plug that into the knowledge base search engine, and the relevant article is the first in the queue. I suppose this “feature” is undocumented, but sheesh, Access 97’s help was a lot better.
I’d stick with using forms, fierra. Try a form in datasheet view.
If that doesn’t work, try a continuous form. Put the text boxes right next to each other and set their Special Effect property to “Flat”. This should mimic a table fairly well and get rid of the autofilling. Feel free to email me if you have any questions.
Yeah, I’m currently trying to figure out why the code for the nifty timeline report doesn’t work anymore. I’m seriously peeved at the idiotic systems people that decided to push this down without making sure that all our database’s were going to work. And I can’t find any good info on why the VB doesn’t work anymore…grumbles…stupid microsoft.
The VB code probably doesn’t work because Microsoft “fixed” a lot of inconsistancies with the VBA from '97 to 2000. I was working for a company doing a database app for the past 3 years or so, and we converted from an older version of Access (2? I think) to 97, then 97 to 2000 (it is a LONG story), but we still had to go and manually change a bunch of things - specifically references to “.” vs “!” - Access 2000 was brought into the more strict Visual Basic standard than it had previously. I don’t remember all the rules of when you use one or the other, but in general “.” means a property or method (function) and “!” means field contained in…
I just thought of something else too. Microsoft starting using a new database interface model (well, I am not sure what you call it) ADO, when the previous versions used something called DAO. ADO doesn’t have all the function calls that DAO did, so some stuff just doesn’t work. This has to be changed in “References” in the code editor. ADO has to be unselected and DAO has to be added. I don’t remember which menu specifically had that though.