Deletes not available

  • Thread starter Thread starter LAS
  • Start date Start date
L

LAS

I have a very simple form, one table as recordsource. Deletes Allowed =
true (and all other such things are true). I open it in datasheet mode. I
can add records OK, but when I right click on the left "column" (don't know
technical term for that spot), the "Delete Row" in the right-mouse menu is
disabled. How can I get it enabled?

TIA
LAS
 
I have a very simple form, one table as recordsource. Deletes
Allowed = true (and all other such things are true). I open it in
datasheet mode. I can add records OK, but when I right click on
the left "column" (don't know technical term for that spot), the
"Delete Row" in the right-mouse menu is disabled. How can I get
it enabled?

Are edits available?
 
Yes, edits and adds.

Just to be sure, you can actually edit existing data and add new
records (just to distinguish from the settings for the AllowEdits
and AllowAdditions properties)?

Is there code running anywhere in the form when it opens?
 
Yes, I can add rows and change existing data. The right mouse menu shows
New Record, Delete Record, Cut, Copy, Paste, Row Height. Of those only
"Delete Record" is disabled (de-emphasized, faded font.)
 
Yes, I can add rows and change existing data. The right mouse
menu shows New Record, Delete Record, Cut, Copy, Paste, Row
Height. Of those only "Delete Record" is disabled (de-emphasized,
faded font.)

If you open the table datasheet directly, not the form based on that
table, can you delete records?
 
Yes, DELETE is available then.
I have several such forms, so the user can simply edit some tables
"directly." They all have the same problem. I made them all the same way,
by making a "garbage" form (just put all the columns on it any old place)
and opening it with

DoCmd.OpenForm rs![Argument], acFormDS, , , acFormReadOnly

I had to go look this up to answer your question, and I think I see where to
investigate. I got this from a "switchboard" form that I got from
someplace. Perhaps it came with Access??? Now the mystery is why I should
be able to add and edit if it has acFormReadOnly !!!!
I will read up on the OpenForm command.
 
DoCmd.OpenForm rs![Argument], acFormDS, , , acFormReadOnly

First I tried using another format that was available in the pre-existing
code....

DoCmd.OpenForm rs![Argument], acFormDS

But that left me with everything disabled except Copy and something else.

So then I tried changing the acFormReadOnly to acFormEdit. Strangely enough
that left me with the same issue.... everything enabled excep DELETE. Any
ideas?
 
Does this help? When I don't use the command to open it, but choose "form"
or "design" or "datasheet" from the navigation pane, in datasheet view,
right mouse gives me "New record, delete record (DISABLED),cut, copy, paste,
row height." Form view gives me all those (delete disabled) except for New
Record, but that's taken care of by the empty record at the bottom.

So the problem is not found in the parameters supplied to DoCmd.OpenForm.

I've checked a jillion times to see that "Allow Deletes" is set to Yes.
 
DoCmd.OpenForm rs![Argument], acFormDS, , , acFormReadOnly

First I tried using another format that was available in the
pre-existing code....

DoCmd.OpenForm rs![Argument], acFormDS

But that left me with everything disabled except Copy and
something else.

So then I tried changing the acFormReadOnly to acFormEdit.
Strangely enough that left me with the same issue.... everything
enabled excep DELETE. Any ideas?

What are the properties of the form itself set to?
 
see below

David W. Fenton said:
DoCmd.OpenForm rs![Argument], acFormDS, , , acFormReadOnly

First I tried using another format that was available in the
pre-existing code....

DoCmd.OpenForm rs![Argument], acFormDS

But that left me with everything disabled except Copy and
something else.

So then I tried changing the acFormReadOnly to acFormEdit.
Strangely enough that left me with the same issue.... everything
enabled excep DELETE. Any ideas?

What are the properties of the form itself set to?

If you mean AllowDeletes , AllowAdds, etc., they are all set to YES. I've
checked it a jillion times.
You'll see from another response of mine that the DoCmd issue can be
ignored. It behaves this way in Datasheet View in the development
environment.
 
see below

David W. Fenton said:
DoCmd.OpenForm rs![Argument], acFormDS, , ,
acFormReadOnly

First I tried using another format that was available in the
pre-existing code....

DoCmd.OpenForm rs![Argument], acFormDS

But that left me with everything disabled except Copy and
something else.

So then I tried changing the acFormReadOnly to acFormEdit.
Strangely enough that left me with the same issue.... everything
enabled excep DELETE. Any ideas?

What are the properties of the form itself set to?

If you mean AllowDeletes , AllowAdds, etc., they are all set to
YES. I've checked it a jillion times.

Is DataEntry OFF?
You'll see from another response of mine that the DoCmd issue can
be ignored. It behaves this way in Datasheet View in the
development environment.

I'm stumped.

Can you create a sample database that demonstrates the problem? A
few records from your main table and the form itself should be all
that's needed to see the problem. I'd be happy to look at it to see
if I can figure it out.

Of course, that works OK, it might help you identify the source of
the problem.
 
Yes, I will. How do I get it to you? Can put an attachment on a post?
I've never seen one.

David W. Fenton said:
see below

David W. Fenton said:
DoCmd.OpenForm rs![Argument], acFormDS, , ,
acFormReadOnly

First I tried using another format that was available in the
pre-existing code....

DoCmd.OpenForm rs![Argument], acFormDS

But that left me with everything disabled except Copy and
something else.

So then I tried changing the acFormReadOnly to acFormEdit.
Strangely enough that left me with the same issue.... everything
enabled excep DELETE. Any ideas?

What are the properties of the form itself set to?

If you mean AllowDeletes , AllowAdds, etc., they are all set to
YES. I've checked it a jillion times.

Is DataEntry OFF?
You'll see from another response of mine that the DoCmd issue can
be ignored. It behaves this way in Datasheet View in the
development environment.

I'm stumped.

Can you create a sample database that demonstrates the problem? A
few records from your main table and the form itself should be all
that's needed to see the problem. I'd be happy to look at it to see
if I can figure it out.

Of course, that works OK, it might help you identify the source of
the problem.
 
When I try to post a response with DeleteProblem.mdb_file as attachment I
get this error. Outlook Express has been flakey in the last few weeks. Do
you know if it's worth continuing to try this way? Or might there be a
different way to get you the database? (Fortunately a barebones db
reproduces the problem. Open the only form. Choose datasheet view.

Outlook Express could not post your message. Subject 'Re: Deletes not
available', Account: 'news.eternal-september.org', Server:
'news.eternal-september.org', Protocol: NNTP, Server Response: '441 437
Binary: misplaced mdb_', Port: 119, Secure(SSL): No, Server Error: 441,
Error Number: 0x800CCCA9
David W. Fenton said:
see below

David W. Fenton said:
DoCmd.OpenForm rs![Argument], acFormDS, , ,
acFormReadOnly

First I tried using another format that was available in the
pre-existing code....

DoCmd.OpenForm rs![Argument], acFormDS

But that left me with everything disabled except Copy and
something else.

So then I tried changing the acFormReadOnly to acFormEdit.
Strangely enough that left me with the same issue.... everything
enabled excep DELETE. Any ideas?

What are the properties of the form itself set to?

If you mean AllowDeletes , AllowAdds, etc., they are all set to
YES. I've checked it a jillion times.

Is DataEntry OFF?
You'll see from another response of mine that the DoCmd issue can
be ignored. It behaves this way in Datasheet View in the
development environment.

I'm stumped.

Can you create a sample database that demonstrates the problem? A
few records from your main table and the form itself should be all
that's needed to see the problem. I'd be happy to look at it to see
if I can figure it out.

Of course, that works OK, it might help you identify the source of
the problem.
 
How do I get it to you?

Don't you have any webspace available to you anywhere? If not, you
could put it on YouSendit.com. You can go to me website to email me
the link.
 
I've just gotten an account on DropBox.com, which looks like it might do the
trick, but I'll have to study up on it. More later.
 
Back
Top