I figured it out, but thanks anyway ______________________________________________ "I'm not me when I dream...anymore." -TRUSTcompany

Thanks Ray that kinda helps... but i'm still not sure why i'm doing that... Maybe i didnt explain it good enought.. I making an array, that has 3 members (name, genre, rating) Overall i want a little menu 1) Add a game 2) Display a game 3) Show average rating of games 4) Quit Something like that..so first i made a sub prodecure that displayed this menu (so i can call it after each option the user makes), that was all good So the sub main looks like this so far Private Sub Main() Dim gamesArray() as Game 'Game is a declared structure above sub main) Dim choice as integer call DisplayMainMenu() choice = console.readline() End Sub So then I started to do this: Private Sub Main() Dim gamesArray() as Game 'Game is a declared structure above sub main) Dim choice as integer call DisplayMainMenu() choice = console.readline() If choice = 1 then * call AddGame() End if End Sub Private Function AddGame() console.write("Enter the game name: ") name = console.readline() console.write("Enter the genre: ") genre = console.readline() console.write("Enter the games rating: ") rating = console.readline() End Function *** So my question being, if i get the info for the game in the function.. i somehow need to get all 3 pieces back up into the array... Hope this clarifies things...:-D EDIT: Sorry forgot the IF ______________________________________________ "I'm not me when I dream...anymore." -TRUSTcompany

Giles wrote: For the C++ standards guys to implement this, it would need to be more aware of the system and threading architecture. I don't think so actually. All you need is a conditional. Shouldn't be that tricky, should it? Also, the standards guys only have to specify the behaviour, it's up to the compiler/runtime guys to implemented. And furthermore, they could make this a compiler option just like exceptions and RTTI. Giles wrote: How would you implement it? I've just had a thought that you would have to implement an extra byte/flag on the V-Table and make use of an OS specific sync model to make sure that you could identify when to call the static constructor. You wouldn't want it in the vtable, since there is nothing virtual about this - it's per class instance, not object instance. So you could shove a bit into a possibly already existing bit vector into the class information block. CLASS_OPT_STATIC_CONSTRUCTOR_ON_THIS_BRANCH = 1 -> Start executing static initializers from top to bottom. Of course, the entire inheritance chain from root to this-class needs to be locked, but that's obvious if you think/draw pictures about it. Giles wrote: but to integrate in to the language in a cross platform way is more tricky. e.g. a real time OS. I don't see the problem actually. There are threaded and non-threaded environments. The non-threaded environments we don't need to consider - the fact that they are non-threaded makes the implementation easy as pie. Threaded environments need only support one thing: conditionals. If they don't, then something's terribly f-ed up in that environment. It's like having files and file systems, but in no way provide a way to open/create files. Cross platform differences are solved in runtime libraries. It's done that way today, and it works just fine.. doesn't it? :~ If I wasn't so damn lazy I think I could pull this one off using GCC. (If it hasn't already been done that is). -- "It is amazing how f-ing crazy I really am."

Ok, here you go… http://samples.gotdotnet.com/quickstart/[^] http://www.vb-helper.com/tutorial.htm[^] http://www.vbwm.com/resources/default.asp?page=TutorialsVBNET[^] http://www.troobloo.com/tech/vbdotnet.shtml[^] Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall." George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things."

Sorry for not responding dude, but really now.... There are examples on how to create/call functions in VB everywhere. Just download just about any sample VB code and you will see a sample of how to write and consume a function. I did not answer this question because I felt that it was asked by someone that clearly needed to do some looking around themselves on the subject. Sorry... Looking at the responses that you did get and what you found on your own you got the concept. Just please remember that no one here OWES anyone an answer. Just as a personal note… I hate function that have byref arguments. They are used alot in the Windows world and I still hate them. IMHO functions take in arguments and return a value. That is the pure way of thinking about it. When you use a function you always think of it as: returnValue = FunctionName(arg1, arg2, … argn) And the function looks as follows: <scope> Function FunctionName(arg1 As Type, arg2 As Type, … argn As Type) As ReturnType 'define the return value to use Dim retVal as ReturnType 'perform what ever calculations you need to do 'set the return value retVal = answerToCalculation Return ReturnType 'if you are using VB.NET FunctionName = answerToCalulation 'if you are using VB6 End Function The number of input args are up to what you need, and it is very clear as to what is being returned and where. Using ByRef is called output arguments. I don't like them at all. X| As I see it, if the returned values does not end up on the left side of a function call then it is not a function, it is a Subroutine. Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall." George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things."