I am porting am application from Access to VB.NET and am considering the best practice for storing 'global' variables for strings, integers etc and even forms.
I have done some research and can see that it is possible to create a standard module in vb.net to store the global variables (as used in Access & VB6). Is this an acceptable method or are there any reasons why this should not be used and if so how should this be done?
Looking at forms, I have a few forms that are never closed and should only ever have one instance. I have seen that this can be accomplished by creating a singletion class member for the form and refering to this class. However, I have also tried simply adding "Public frmMyForm as New frmMyForm" into the standard global variables module and this emmes to work fine, I simply refernce this from the other forms and classes in my project. Is there a reason why this is not good practice as it seems a very simple way of achieving what I need!.