|
-
Dec 1st, 2003, 06:56 PM
#1
Thread Starter
Addicted Member
-
Dec 1st, 2003, 08:34 PM
#2
Why would you need to do that?
-
Dec 1st, 2003, 08:37 PM
#3
Originally posted by MartinLiss
Why would you need to do that?
Just incase you had memory lapses when coding 
Sorry Paul 
Bruce.
-
Dec 1st, 2003, 11:06 PM
#4
Perhaps you should explain what you're trying to accomplish?
-
Dec 1st, 2003, 11:41 PM
#5
PaulTilley
I don't believe so... But the compiler will.
-
Dec 2nd, 2003, 05:32 PM
#6
Thread Starter
Addicted Member
No its not because I have a bad memory.
No Its not because I have a bad memory.
Oops...
NE Way, its because from a module I need to call a sub on a form. There are many forms with the same sub name within. Some forms do not have this sub at all, and this is what I need to test.
Your comments have made me realise though, that there is another better way of approaching this problem.
Im about to check it out now.
Ta all.
-
Dec 2nd, 2003, 10:30 PM
#7
Originally posted by PaulTilley
No its not because I have a bad memory.
No Its not because I have a bad memory.
Oops...
NE Way, its because from a module I need to call a sub on a form. There are many forms with the same sub name within. Some forms do not have this sub at all, and this is what I need to test.
Your comments have made me realise though, that there is another better way of approaching this problem.
Im about to check it out now.
Ta all.
Calling a form's sub from a module. *sounds* a little inefficient to me, and I'm sure there's a more optimized way of doing the same.
But anyways, you can delcare the sub as public, and call it like
Form3.SubName()
HTH
-
Dec 2nd, 2003, 11:40 PM
#8
He mendhak, Who kissed you.... No that's all wrong... Kiss a frog it turns into a Prince
Good looking Avatar
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote
2009 - 2016
