Prevent user to type on Autonumber

Hello,

Although it says autonumber, users have tendency to type it. My question is
how can we prevent the user to type it ( unable to type that field in the
form) even we can assign the cursor passes it go to the next field.

Thanks in advance
--
H. Frank Situmorang

Make the control locked.

In design view, select the control,
on property dialog | Data tab | Locked - set to true

Jeanette Cunningham

"Frank Situmorang" wrote in message
...
Hello,

Although it says autonumber, users have tendency to type it. My question
is
how can we prevent the user to type it ( unable to type that field in the
form) even we can assign the cursor passes it go to the next field.

Thanks in advance
--
H. Frank Situmorang

Thanks Jeannette for your quick answer. But will it not make autonumber not
to work?/update the table?
--
H. Frank Situmorang


"Jeanette Cunningham" wrote:

Make the control locked.

In design view, select the control,
on property dialog | Data tab | Locked - set to true

Jeanette Cunningham

"Frank Situmorang" wrote in message
...
Hello,

Although it says autonumber, users have tendency to type it. My question
is
how can we prevent the user to type it ( unable to type that field in the
form) even we can assign the cursor passes it go to the next field.

Thanks in advance
--
H. Frank Situmorang

Setting it to Locked, stops users from changing it only. Behind the form it
will work as normal, only the user is prevented from interfering where they
are not welcome.
Test it out. Set it to Locked and test it with a new record and see how well
it works.

Jeanette Cunningham


"Frank Situmorang" wrote in message
...
Thanks Jeannette for your quick answer. But will it not make autonumber
not
to work?/update the table?
--
H. Frank Situmorang


"Jeanette Cunningham" wrote:

Make the control locked.

In design view, select the control,
on property dialog | Data tab | Locked - set to true

Jeanette Cunningham

"Frank Situmorang" wrote in message
...
Hello,

Although it says autonumber, users have tendency to type it. My
question
is
how can we prevent the user to type it ( unable to type that field in
the
form) even we can assign the cursor passes it go to the next field.

Thanks in advance
--
H. Frank Situmorang

Jeanette is pretty much correct. It would also be useful to set the Enabled
property to No, also, so tabbing will bypass it.

But, I do not allow users to see autonumber fields. I have them on the
form, but made Not Visible and no tab stop. There is absolutely no reason
for an autonumber field used as a primary key to by visible to a user.

--
Dave Hargis, Microsoft Access MVP


"Frank Situmorang" wrote:

Thanks Jeannette for your quick answer. But will it not make autonumber not
to work?/update the table?
--
H. Frank Situmorang


"Jeanette Cunningham" wrote:

Make the control locked.

In design view, select the control,
on property dialog | Data tab | Locked - set to true

Jeanette Cunningham

"Frank Situmorang" wrote in message
...
Hello,

Although it says autonumber, users have tendency to type it. My question
is
how can we prevent the user to type it ( unable to type that field in the
form) even we can assign the cursor passes it go to the next field.

Thanks in advance
--
H. Frank Situmorang

While Klatuu's advcie about even showing an autonumber is spot on, I'm
confused by the queation itself! An Autonumber is never editable, whether you
explicitly "Lock" the field or not!

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/200803/1

It would just avoid throwing an error if a user tried to edit it.
--
Dave Hargis, Microsoft Access MVP


"Linq Adams via AccessMonster.com" wrote:

While Klatuu's advcie about even showing an autonumber is spot on, I'm
confused by the queation itself! An Autonumber is never editable, whether you
explicitly "Lock" the field or not!

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/200803/1