Critique this method

[Creosote]

This is in C#. The concept would apply to VB.Net or any other OO language such as Java though.

I have a form that displays data in combo boxes and text boxes from a data base. It lets the user navigate via the combo boxes. Based on the statistics of the records, it performs an algorithm to come up with a score.

Anyways, thats the main form the user uses. I have another form to add more records. The statistics for the new records are all generated radomly except one field. On this form, I have a button to genereate a new set of random stats if they don't like the ones they have been given. But I only give them 3 chances to go with what they want.

This is my problem: I need my program to remember how many times a user has generated new random statistics. If they've done it more than 3 times, they will have to close out the program and re-open it to 'cheat.'

This is some rough pseudocode of what happens (intCount keeps track of how many times a user has re-generated random stats):

On Create Reocrd Click:
--->Open frmCreate modally
------>Enter/Save new Records
------>On frmCreate.Closing
--------->Cancel closing
--------->Hide frmCreate
--->Add intCount from frmCreate to intCount on frmMain
--->Destroy frmCreate
--->Requery for new records on frmMain
End

When frmCreate is hidden, it allows frmMain to go on with its process, the first of which is adjusting the intCount figure so I can keep track of it for the duration of the program. If I would have not cancelled frmCreate's closing, then I would have lost frmCreate's intCount.

This works great, but....I am thinking there should be a better method for this. When frmMain is once again the visible form, you can see the form being repainted from the top to the bottom, kind of like a java applet.

Before I was keeping track of and letting users create an infinate number of random stats, when frmCreate would close, frmMain would be on the screen without that 'repainting' effect.\

Its a minor thing, and I can live with it, but I was just wondering if anyone had any ideas.

[vass0922]

maybe keep a static int variable in the click procedure where the form is opened?

[Creosote]

But I may or may not be wanting to add to my intCount. For example, is someone opens up the frmCreate, and closes it right away, then they've wasted one chance.

If they re-generate the stats while in frmCreate, then they've wasted 2 chances.

I would need a way to reference frmMain from frmCreate, but that's impossible. It would would if I was destroying frmMain when I was open frmCreate, then on closing frmCreate, making a new frmMain, but I don't want to do that either.

[vass0922]

maybe put the int in a module (not sure what they are in C#) and make it public so both forms can modify it on the fly?
ok, believe C would use a class .. could make it a property that you could set/retrieve?

[Creosote]

I know what you're saying. If it was VB6, I would have used a module, and the every other form would know that modules variables.

I do not think, or I haven't found, anything similar in C#. This program does have non-form classes that I've made to do algorithims and return values based on those algorithms. However, you have to create an instance of each class.

Example:

Class1 c1 = new Class1();
c1.setMethod(arguements);
variable = c1.getMethod();


But say I made a new instance of a varible-keeping class in frmMain. I don't know how I would access that same instance in frmCreate.

I'm not even sure if VB.Net has modules anymore.

[vass0922]

yup, still has modules

hmmm
maybe make a public int in the first form?
or you could pass the object as a param *shrug*

[Creosote]

Actually, I read somewhere on another forum, and I think you're right. Making a static variable might not make you need to create an instance of a class. I'm gonna try it out.

Thanks