When using the SaveSetting command the parameters are as follows:
Since they are all strings (same as GetSetting parameters are), then how come something like this will work:Code:SaveSetting (AppName[String], Section[String], Key[String], Setting[String])
orCode:SaveSetting "Some Program", "Section 1", "5", "1"
Without a type mismatch error happening.Code:Check1.Value = GetSetting("Some Program", "Section 1", "5", "1")
But if i have a Function with the following in it...
and pass integers into it, it will error with type mismatch.Code:Public Function SomethingToDo (FirstParameter As String, SecondParameter As String) As String
How does visual basic get around this? I don't want to use Variants because problems will come when i'm converting back to integers or what ever. So what would i put inside the function parameters to make it "fuzzy"?




Reply With Quote