Just installed A2010, and have an immediate and critical problem.
This only happens with an unbound control that has a Default Value specified. Whether or not the form is bound doesn't seem to make a difference.
The problem is that I can't enter a Null value into this unbound control! I remove the current value, but as soon as I move off the control Access restores it with the Default Value. Even if I put another value in first and then try to remove that, it returns to the Default Value.
Anyone know of this? Anyone know a solution?
Unbound Control problem in Access 2010
-
- 3StarLounger
- Posts: 331
- Joined: 11 Feb 2010, 03:55
- Location: Land O Lakes, FL
Unbound Control problem in Access 2010
Mark Liquorman
Land O Lakes, FL
see my website http://www.liquorman.net for Access Tips and Tricks, and for my Liquorman Utilities.
Land O Lakes, FL
see my website http://www.liquorman.net for Access Tips and Tricks, and for my Liquorman Utilities.
-
- Administrator
- Posts: 78596
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Unbound Control problem in Access 2010
Apparently this is a bug in Access 2010 - it's also mentioned in Cannot have Null if there is a Default Value in a control in A2010. MVP datAdrenaline suggests clearing the DefaultValue property in the After Update event of the control.
Best wishes,
Hans
Hans
-
- 3StarLounger
- Posts: 331
- Joined: 11 Feb 2010, 03:55
- Location: Land O Lakes, FL
Re: Unbound Control problem in Access 2010
I had done all sorts of search and hadn't found any other mention of this anywhere; but often this means I didn't enter the right combination of words to find it. But especially important is that I can't find any mention of this on the MSKB or anything else related to Microsoft to indicate they know about it.HansV wrote:Apparently this is a bug in Access 2010 - it's also mentioned in Cannot have Null if there is a Default Value in a control in A2010. MVP datAdrenaline suggests clearing the DefaultValue property in the After Update event of the control.
Unfortunately, clearing the DefaultValue in the AfterUpdate event may work OK for a single control, but it is not really a practical solution when talking about a database-wide problem.
I recently posted this on the "Microsoft Answers" website. If I find out anything there I'll post it here.
Mark Liquorman
Land O Lakes, FL
see my website http://www.liquorman.net for Access Tips and Tricks, and for my Liquorman Utilities.
Land O Lakes, FL
see my website http://www.liquorman.net for Access Tips and Tricks, and for my Liquorman Utilities.
-
- Administrator
- Posts: 78596
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Unbound Control problem in Access 2010
Microsoft closely monitors the Utter Access forums, and since an Access MVP replied, I assume that Microsoft knows about the problem by now. Hopefully, it'll be corrected in an update, or perhaps in Office 2010 SP1.
Best wishes,
Hans
Hans