Disabled New Record Button

Hello all!

I'm having a problem with one (yes, just one) of my forms in my Access
project. The new record button is disabled and I don't know why. The
AllowAdditions flag = true on the form. Is there anything else I'm missing? I
tried setting Me.AllowAdditions = True in the Activate method and set a
breakpoint there and haven't gotten the app to stop on the breakpoint to
ensure this flag is true. While I'm waiting on some help, this just inspired
me to try some other events to set the flag in.

Thanks in advance!!
--
AT

If you open the query that the form is based on, can you add records
directly in the query? If not, then you won't be able to in the form either.
Also, it will be disabled if you're already at a new record, such as when
opening a form that has no records.

--
Wayne Morgan
Microsoft Access MVP


"atrapp" wrote in message
...
Hello all!

I'm having a problem with one (yes, just one) of my forms in my Access
project. The new record button is disabled and I don't know why. The
AllowAdditions flag = true on the form. Is there anything else I'm
missing? I
tried setting Me.AllowAdditions = True in the Activate method and set a
breakpoint there and haven't gotten the app to stop on the breakpoint to
ensure this flag is true. While I'm waiting on some help, this just
inspired
me to try some other events to set the flag in.

Thanks in advance!!
--
AT

Wayne,
In your form properties, change the Recordset Type from Dynaset to Dynaset
(inconsistent updates). This will allow you to add records even if you can't
add them in the query.

"Wayne Morgan" wrote:

If you open the query that the form is based on, can you add records
directly in the query? If not, then you won't be able to in the form either.
Also, it will be disabled if you're already at a new record, such as when
opening a form that has no records.

--
Wayne Morgan
Microsoft Access MVP


"atrapp" wrote in message
...
Hello all!

I'm having a problem with one (yes, just one) of my forms in my Access
project. The new record button is disabled and I don't know why. The
AllowAdditions flag = true on the form. Is there anything else I'm
missing? I
tried setting Me.AllowAdditions = True in the Activate method and set a
breakpoint there and haven't gotten the app to stop on the breakpoint to
ensure this flag is true. While I'm waiting on some help, this just
inspired
me to try some other events to set the flag in.

Thanks in advance!!
--
AT

You're right, it will. But, the reason Access doesn't allow this by default
is because you may do something that won't maintain the integrity of your
data. If you control this problem yourself, then that is sometimes the
easiest way out.

--
Wayne Morgan
Microsoft Access MVP


"ihatepaperwork" wrote in message
...
Wayne,
In your form properties, change the Recordset Type from Dynaset to Dynaset
(inconsistent updates). This will allow you to add records even if you
can't
add them in the query.

The form's record source is a table in MS SQL Server.

"Wayne Morgan" wrote:

If you open the query that the form is based on, can you add records
directly in the query? If not, then you won't be able to in the form either.
Also, it will be disabled if you're already at a new record, such as when
opening a form that has no records.

--
Wayne Morgan
Microsoft Access MVP


"atrapp" wrote in message
...
Hello all!

I'm having a problem with one (yes, just one) of my forms in my Access
project. The new record button is disabled and I don't know why. The
AllowAdditions flag = true on the form. Is there anything else I'm
missing? I
tried setting Me.AllowAdditions = True in the Activate method and set a
breakpoint there and haven't gotten the app to stop on the breakpoint to
ensure this flag is true. While I'm waiting on some help, this just
inspired
me to try some other events to set the flag in.

Thanks in advance!!
--
AT

Wayne,

Your comment gives me an idea. Could incorrect integrity settings cause this
to happen (e.g., not setting index and/or identity properties correctly)?

"Wayne Morgan" wrote:

You're right, it will. But, the reason Access doesn't allow this by default
is because you may do something that won't maintain the integrity of your
data. If you control this problem yourself, then that is sometimes the
easiest way out.

--
Wayne Morgan
Microsoft Access MVP


"ihatepaperwork" wrote in message
...
Wayne,
In your form properties, change the Recordset Type from Dynaset to Dynaset
(inconsistent updates). This will allow you to add records even if you
can't
add them in the query.

Thanks but in my Recordset Type field, the only two choices that I have are
snapshot and updatable snapshot (could be the fact that it's an .adp file,
maybe??)

AT

"ihatepaperwork" wrote:

Wayne,
In your form properties, change the Recordset Type from Dynaset to Dynaset
(inconsistent updates). This will allow you to add records even if you can't
add them in the query.

"Wayne Morgan" wrote:

If you open the query that the form is based on, can you add records
directly in the query? If not, then you won't be able to in the form either.
Also, it will be disabled if you're already at a new record, such as when
opening a form that has no records.

--
Wayne Morgan
Microsoft Access MVP


"atrapp" wrote in message
...
Hello all!

I'm having a problem with one (yes, just one) of my forms in my Access
project. The new record button is disabled and I don't know why. The
AllowAdditions flag = true on the form. Is there anything else I'm
missing? I
tried setting Me.AllowAdditions = True in the Activate method and set a
breakpoint there and haven't gotten the app to stop on the breakpoint to
ensure this flag is true. While I'm waiting on some help, this just
inspired
me to try some other events to set the flag in.

Thanks in advance!!
--
AT

Ok, we have 3 replies here, let me see if I can put them together.

1) I doubt that the indexing would cause your problem, but the integrity
settings might. I'm not familiar enough with SQL server to help you with it.

2) A snapshot is NOT updateable. It is a one time, read only, copy of the
records as they appeared at the time the snap shot was taken.

3) You may need to repost your question, mentioning the SQL server so that
someone who uses SQL server will jump in and help.

--
Wayne Morgan
Microsoft Access MVP


"atrapp" wrote in message
...
Wayne,

Your comment gives me an idea. Could incorrect integrity settings cause
this
to happen (e.g., not setting index and/or identity properties correctly)?

"Wayne Morgan" wrote:

You're right, it will. But, the reason Access doesn't allow this by
default
is because you may do something that won't maintain the integrity of your
data. If you control this problem yourself, then that is sometimes the
easiest way out.

--
Wayne Morgan
Microsoft Access MVP


"ihatepaperwork" wrote in
message
...
Wayne,
In your form properties, change the Recordset Type from Dynaset to
Dynaset
(inconsistent updates). This will allow you to add records even if you
can't
add them in the query.

Wayne,

Your comment about integrity sparked a thought! Maybe I didn't set up the
index and/or identity settings properly for the underlying table of the form.
So, lo and behold! I checked the table and it didn't have an index!!!

Thanks so much for your help!!
AT

"Wayne Morgan" wrote:

You're right, it will. But, the reason Access doesn't allow this by default
is because you may do something that won't maintain the integrity of your
data. If you control this problem yourself, then that is sometimes the
easiest way out.

--
Wayne Morgan
Microsoft Access MVP


"ihatepaperwork" wrote in message
...
Wayne,
In your form properties, change the Recordset Type from Dynaset to Dynaset
(inconsistent updates). This will allow you to add records even if you
can't
add them in the query.