Datasheet View - Blank LIne not showing - AllowAdditions = Yes

[arpeggione]

Hi: I have a form in Datasheet view. It used to be that one could just add a new record by typing stuff into the blank line at the bottom. Now there isn't a blank line at the bottom, but I still have AllowAdditions = Yes. Any ideas why?

thank you, Karen

 

[arpeggione]

Ok...I think i figured this one out.....form query join needs to be based on primary key...

 

[TheAceMan1]

How are ya arpeggione . . .

Here's the real problem.

[blue]To tell if the returned [blue]Recordset[/blue] of a [blue]form[/blue] (Allow Additions property set to [purple]Yes[/purple]) or [blue]query[/blue] is [blue]updateable[/blue] have a look at the Record Navigation-[blue]AddNew button[/blue], if it has that disabled look (grayed out) ... then the recordset is uneditable! ... aka no addnew line![/blue]

The following link gives several reasons why:
Why is my query read-only?

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see faq219-2884 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[arpeggione]

Aceman: Thx for your email. I still am pretty sure my problem has to do with joins and primary keys (tables need to be joined on primary key for query to be updateable). I'll confirm later.

As for your note, even though the query is not updateable (ie no blank line at the bottom), the "AddNew" thing at the bottom with the * is NOT greyed out...

those are my thoughts.
thank you,
Karen

 

[TheAceMan1]

arpeggione . . .

Really ... and your using which version?

See Ya! . . . . . .

Be sure to see faq219-2884 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[arpeggione]

ms access 2003...

 

[MazeWorX]

Karen if the form used to work as stated and now it doesn't what makes you think the query now needs to be re written? Just for fun have you tried a 'save as' on the form?

What i'm getting at here is the form may be corrupt?

Thoughts?

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>

 

[arpeggione]

Hi All: I actually am all set with this question at the moment - (see my second email). (No, the form isn't corrupt - and yes, I may use a coded procedure to save, etc).

thank you,

Karen

 

[TheAceMan1]

[blue] ... even though the query is not updateable (ie no blank line at the bottom), [purple]the "AddNew" thing at the bottom with the * is NOT greyed out...[/purple][/blue]

Now were getting somewhere. I've been talking about the [blue]AddNew[/blue] button of the [blue]record navigation buttons[/blue] on the bottom left of the form/query. If the recordsource of the form is updateable it looks like this

. If its disabled it looks like this

. Your telling me the [blue]AddNew[/blue] record selector is enabled

and you have no [blue]addnew[/blue] record line. This is indicitive of corruption as indicated by [blue]MazeWorX[/blue].

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see faq219-2884 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[MazeWorX]

Karen not to beat a dead horse this exact scenario just happened to me with a db I use to track performance data for employees I manage. Turns out the form was corrupt. A simple 'Save As' resolved the issue. The corruption was probably caused by myself as I was using [red]and[/red] developing at the same time as this is an app I will use and have no intention of distributing to multiple users



HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>

 

[arpeggione]

The form is TOTALLY NOT corrupt. When I change the form query to include a primary key in the proper table, everything works properly - really!

I don't have the reference now, but I actually found a list of things that can cause this problem somewhere on the web, and the primary key thing was on the list.

thank you,

Karen

 

[PHV]

Have a look here:

http://support.microsoft.com/kb/148581

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[arpeggione]

And...what I wasn't clear in my writing about is that this thread should be closed. Thanks all, Karen