Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Non-enabled form setting 1

Status
Not open for further replies.

neilmcmor

Technical User
Aug 9, 2007
30
GB
I have a form with all fields enabled option set to No. The user must be allowed to click a delete button to delete a record but cannot edit or add records. Is it possible to prevent the fields from greying out in this situation. I have tried by enabling the fields and instead setting the forms 'Allow Edits', 'Allow Additions' options as No whilst leaving the Allow Deletes to yes but this dos not appear to allow deletess!! Any help would be appreciated
 
Try
Enabled = True
Locked = True
for all the fields

________________________________________________________
Zameer Abdulla
Help to find Missing people
 

How do they delete the record? Using code?
Yo can disallow adding/deleting records if you use DISTINCT, GROUP BY or UNION in your query while all fields are enabled.
 
I've answered this on another site, but since it's posted here as well I'll post here too. That way anyway searching this site can see it. Your strategy with Allow Edits/Allow Additions set to No and Allow Deletions set to Yes should work! My guess is that your form is based on a query, and that your query is Read Only! Take a look at Allen Browne’s white paper at to learn why this could be so!



The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!
 
The form is based directly on a table Missinglinq. But thanks ZmrAbdulla you solution worked it appears.
 

As I said, your strategy with Allow Edits/Allow Additions set to No and Allow Deletions set to Yes should work unless the underlying RecordSource was Read-Only (which is isn't, in this case.) Since this wasn't the case, I did some noodling around and found out that setting AllowDeletions to YES doesn't work if AllowEdits is set to No!

My question to the esteemed members here is this: Is this a bona fide BUG, or just another QOA (Quirk Of Access) and should it be reported to Micro$oft?

The Missinglinq

Richmond, Virginia

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

Reading from help

When the AllowEdits property is set to No, the Delete Record and Data Entry menu commands aren't available for existing records. (They may still be available for new records if the AllowAdditions property is set to Yes.)

It might(?) be translated to: When AllowEdits = No then also AllowDeletions = No

 
From "Help" using what search term, and what version of Access? I tried a number of different search terms in ACC2003.

Still just curious!

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!
 
neilmcmor
you are welcomed

missinglinq
Do you think that my "translation" could be correct? (maybe not the right expression but cant get something to approximate my native 's languange meaning. Sorry)
 

missinglinq,

I just asked you the question, for me to learn something extra. No other reason. If you please, kindly respond.

Thank you.
Jerry
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top