Here's another one:
From the Access Object Dialog Box click on "Modules"
Click on new to make a new module
Copy then paste the following code into the new module:
'################## Beginning of Code #######################
Function SayNo(ByVal N As Currency) As String
Const Thousand...
As the Friendly Ogre said...being able to 'lay hands' on your actual file would help us immensely in helping you! Having said that, though, if by
you mean that after going into the VBA editor then going to Form View the button works...but simply opening the database and then opening the Form...
Paying close attention to everything else you've been told...if you're entering an A or B into the Type control:
If Me.TypeBrand = A
then it has to be Text and the code needs to be
If Me.TypeBrand = "A"
Linq ;0)>
Also, when typing in
Me.txtAge
VBA's IntelliSense should finish it by popping up
Me.txtAgentID
If it doesn't...it means VBA can't find txtAgentID...isn't valid name...perhaps because it's misspelled! It's a good 'spell check,' if you will!
Linq ;0)>
Since nobody else mentioned it...the problem with your code lies here:
Me.textbox2.disabled = True
Notice that Intellisence didn't capitalize the 'd' in disabled! That's because there is no 'disabled' Property!
Arnelgp's codes shows the correct Property here
ctl.Enabled = Nz(Me!Textbox1...
Sorry...but your scenario doesn't make sense! An Unbound Form (i.e. a subform which is unbound) doesn't have any Records (it's Unbound) and so can't have a New Record!
An Unbound Form only contains Unbound Controls, for entering data. This data doesn't become a Record until it is committed a...
You are correct theDBguy...at least thru v2007. I found this workaround in an ancient file in my archives:
The workaround for this is to create two forms.
On FormA have your original tabbed control.
On FormB place a tabbed control. This will be the tabbed control within a tabbed control...
I tend to agree with others, here, in that simple is usually better!
You have to keep in mind that Access is for developing business database applications! You want your interface to be professional looking...not looking like a webpage or an online catalog!
Color is sometimes...
Or better yet, in the same button you use to open the Table, prior to the code that does that, use
If Me.Dirty Then Me.Dirty = False
But as has been said...you really should replace the Table with a simple Form, such as a Datasheet View Form, that looks just like a Table.
Linq ;0)>
Not sure what the
SendKeys " ", True
is supposed to be doing (?setting SendKeys to nothing?)
but try replacing it with
Sendkeys "{NUMLOCK}", True
and see what happens.
Linq ;0)>