[conclusionsend]

Hi.
Is it possible to call a function in one form from a different form?
At the moment I have two forms called Edit and Start. I want to run a function called FileOpen in the Edit form from a control in the Start form.
I tried the code bellow but it doesn't work.

Edit.FileOpen

Thanks.

[born2c0de]

The Function call you provided will work, but ensure that you set your function as Public and not Private.

[conclusionsend]

born2c0de, on 7 Sep, 2006 - 06:07 AM, said:

The Function call you provided will work, but ensure that you set your function as Public and not Private.

Thanks man... I should have known that really

[Louisda16th]

born2c0de, on 7 Sep, 2006 - 06:37 PM, said:

The Function call you provided will work, but ensure that you set your function as Public and not Private.

Yes but while calling a function in a form module from another form module u say:

<variable>= <formname>.function()

[born2c0de]

Louisda16th, on 8 Sep, 2006 - 09:07 AM, said:

born2c0de, on 7 Sep, 2006 - 06:37 PM, said:

The Function call you provided will work, but ensure that you set your function as Public and not Private.

Yes but while calling a function in a form module from another form module u say:

<variable>= <formname>.function()

Only if you're calling a Function (which in VB has to return a value).

You can omit the assignment to the variable in case you are calling a Subroutine.

[Louisda16th]

conclusionsend did say its a function.

This post has been edited by Louisda16th: 08 September 2006 - 09:11 PM

[born2c0de]

That type of function call is optional at times where the return value is unimportant.

For example, the Simple Msgbox Function

Msgbox "ASDF"

Can be called without accepting a return value. Msgbox is a function, and hell yea, it does return a value.

Only when you give parameters about the number of buttons in Msgbox(), the return value gains importance(which would indicate if OK or Cancel etc was pressed) and hence it is required to accept the return value or else VB will not compile.


And besides, when the function call is like this:

Form_name.Func
--or--
Call Form_name.Func

You do not need to accept a return value depending on its importance.

But it is mandatory to do it if your function call is:

Form_Name.Func()

Hope you get things clearly now.

And check this example out....Functions can also be declared and used like this:

Private Sub Command1_Click()
	Dim x As Byte
	
	x = func1
	' Default Return Value Zero
	
	func1	  ' Allowed
	Call func1 ' Allowed
	func1()	' Not Allowed
	x = func1() ' Allowed
	
	

	

End Sub

' This Declaration is ok.
Public Function func1()
MsgBox "Howwzat?"
End Function

This was based on the term 'function' in C/C++ where every user-defined block of code outside main() or other functions is a Function irrespective of whether it returns a value or not.

It doesn't matter because if the return value is required, all the callee function does is read the value of EAX register.
And if it doesn't, EAX is not read or overwritten after the function is called.