What do you mean by "declare a Form event" and what by "calling the form control"? - These statement make no sense to me in this context.
Did you know that you can address a form control directly in this way. Instead of a long reference like Forms!FormX.SubFormContainer.Form.txtControl . You can skip all the hassle, and you get intellisense, i think it's pretty amazing..
First and foremost you are challenging our patience by ignoring questions and comments and instead reiterating vague statements that most likely are incorrect.
Never heard of "declaring an event". You can define a custom event
Public Event SomeEventI googled this to see if this terminology is use in other OOP languages. You can "instantiate' an object of a class. You can "declare" a class variable, but never heard the term "activate a class". The term "activate" is used in Access to refer to an object such as a form receiving the focus. See
Not sure what that means. I assume that means that the "Events raised by a control can be handled"
The only thing I can guess is that you think it is closed, but it is not.
Dim myFrm as Form_FrmCustomers
set myFrm = New Form_FrmCustomersThe only thing I could think of, that would not go out of scope when closing the database, is to append something to the database properties collection. Not that I would do it but you technically could.
Oke@MsAccessNL
It is pretty hard to take-on a this challenge since as pointed out by @sonic8 you are using in imprecise and meaningless language. I understand that maybe some of this is lost in translation from Dutch to english, but it makes it hard to know what you mean.
Never heard of "declaring an event". You can define a custom event
If you want to learn about precise language about events read this. I wrote this because there is often a lot of poor terminology here when people talk about events, event handlers, event procedures.Code:Public Event SomeEvent
What You Need to Know About Access Events
There is often a lot of confusion about Access Events and often answering questions posed here is difficult because of inaccurate terminology. People often say "Event" when it is unclear if they mean the actual event that takes place, the event procedure, or the event property. This thread...www.access-programmers.co.uk
I googled this to see if this terminology is use in other OOP languages. You can "instantiate' an object of a class. You can "declare" a class variable, but never heard the term "activate a class". The term "activate" is used in Access to refer to an object such as a form receiving the focus. See
Not sure what that means. I assume that means that the "Events raised by a control can be handled"
Bottom line is you are incorrect and the following is not true.
The only thing I can guess is that you think it is closed, but it is not.
You cannot instantiate a form's class without also opening the form!!!
If you are referring to
Code:Dim myFrm as Form_FrmCustomers set myFrm = New Form_FrmCustomers
The above syntax creates an instance of the form customers and sets it visible property to false. So it is Open not Closed.
Since you cannot properly describe the challenge, maybe post some code and we can see what you mean.
@isladogs posts some really good well articulated challenges on this forum. Most have to do with security. Here is one
Combobox Zombies Puzzle
Here's a little puzzle for anyone interested. It is based on a similar item posted at the DBGuy's website 3 years ago which he was unable to explain. As I like riddles(!) I worked out how it was done and am posting a modified version here with his permission. The attached database contains...www.access-programmers.co.uk
This helped to answer the below thread
Solved - Combos set up with a 'Value List' : the 'Row Source' ellipses have disappeared !?
Must say I've never seen this happen before, but : I've a combo box set up with a Value List ('Row Soiurce Type : 'Value List') on a Form, and until today it was working well; no problems. Today, for some unknown reason, the 'Row Source' ellipsis has disappeared. ('Data' tab > 'Row Source')...www.access-programmers.co.uk
Thank you for the information. The hidden form is the possible answer. The strange thing is that if, I only Put: Form_F_Test_txtTest = “Hallo” into the immediate window, this statement alone opens a hidden form. So if you would make a bound form, the value Form_Public.Firstname could be used everywhere like a public variable and would probably hold his value even after closing or with an error in the vba code.@MsAccessNL
It is pretty hard to take-on a this challenge since as pointed out by @sonic8 you are using in imprecise and meaningless language. I understand that maybe some of this is lost in translation from Dutch to english, but it makes it hard to know what you mean.
Never heard of "declaring an event". You can define a custom event
If you want to learn about precise language about events read this. I wrote this because there is often a lot of poor terminology here when people talk about events, event handlers, event procedures.Code:Public Event SomeEvent
What You Need to Know About Access Events
There is often a lot of confusion about Access Events and often answering questions posed here is difficult because of inaccurate terminology. People often say "Event" when it is unclear if they mean the actual event that takes place, the event procedure, or the event property. This thread...www.access-programmers.co.uk
I googled this to see if this terminology is use in other OOP languages. You can "instantiate' an object of a class. You can "declare" a class variable, but never heard the term "activate a class". The term "activate" is used in Access to refer to an object such as a form receiving the focus. See
Not sure what that means. I assume that means that the "Events raised by a control can be handled"
Bottom line is you are incorrect and the following is not true.
The only thing I can guess is that you think it is closed, but it is not.
You cannot instantiate a form's class without also opening the form!!!
If you are referring to
Code:Dim myFrm as Form_FrmCustomers set myFrm = New Form_FrmCustomers
The above syntax creates an instance of the form customers and sets it visible property to false. So it is Open not Closed.
Since you cannot properly describe the challenge, maybe post some code and we can see what you mean.
@isladogs posts some really good well articulated challenges on this forum. Most have to do with security. Here is one
Combobox Zombies Puzzle
Here's a little puzzle for anyone interested. It is based on a similar item posted at the DBGuy's website 3 years ago which he was unable to explain. As I like riddles(!) I worked out how it was done and am posting a modified version here with his permission. The attached database contains...www.access-programmers.co.uk
This helped to answer the below thread
Solved - Combos set up with a 'Value List' : the 'Row Source' ellipses have disappeared !?
Must say I've never seen this happen before, but : I've a combo box set up with a Value List ('Row Soiurce Type : 'Value List') on a Form, and until today it was working well; no problems. Today, for some unknown reason, the 'Row Source' ellipsis has disappeared. ('Data' tab > 'Row Source')...www.access-programmers.co.uk
I noted you marking your code as "pseudo code". Nonetheless, I need to nitpick because it is at the very heart of the matter: There is no Open method for a Windows.Forms.Form class!
Yes I probably should have been more specific but I unfortunately thought too much information would confuse the issue, so I kept the idea as pseudo code. But yes showdialog it what I was referring. I often have a parameterized contructors and then want to return values when the form is closed
Public Sub New(ByVal CurrentName As String, ByVal AvailableVars As LP_VariableCollection)
InitializeComponent()
_CurrentName = CurrentName
_NewName = CurrentName
_LPVars = AvailableVars
End Sub Private Sub BtnAdd_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BtnAdd.Click
Dim frm As New frmEditVariableName(getMaxXi, _LPVars)
frm.ShowDialog()
If Not frm.DialogResult = vbCancel Then
addVariable(frm.NewName)
End If
frm.Dispose()
End Sub
