When I am using functions and variables I am used to see that VBA corrects the notation. Then I know, that my coding is recognized by VBA. But VBA doesn't do this for my functions and variables declared in my .xlam. Even after compile there is no correction. The code works as expected, but this confuses me really much.
Is there anything to specify, that this works properly or do I have to live with this lack ?
Office 365 on MacOS
These produce exactly the same result.
You will not see the above when it executes.
Please Login or Register to view this content.
You will see all the action for the above code although it might just appear as fliker onthe monitor. Direct coding as in the first example shows very little if any updating on the monitor screen. But the Select and Activate method of coding does show the updates on screen step by step.Please Login or Register to view this content.
Any code provided by me should be tested on a copy or a mock up of your original data before applying it to the original. Some events in VBA cannot be reversed with the undo facility in Excel. If your original post is satisfied, please mark the thread as "Solved". To upload a file, see the banner at top of this page.
Just when I think I am smart, I learn something new!
Maybe I did not explain exactly.
In my .xlam there is following Code:
But when I use this code and enter normally without capital letters, the notation will be not changed by VBA:Please Login or Register to view this content.
Normalls VBA would change this to:Please Login or Register to view this content.
If getDate(myString) = True Then myDate = getDateValue
Is there more to this that was not posted? This would not produce a result as it is shown here. It needs some more lines of code to determine if 'getdate' is True or False and assign the appropriate value back to 'getdate'. So when your If statement executes, the 'getdate' function is probably returning an empty string or empty value for 'myString' . As for entering capital letters in the function call, it should automatically revert to the same case as the actual function. But UDF should all be in one of the numbered code modules for effedtive use.Please Login or Register to view this content.
Sorry again
As above-mentioned the function executes as expected with precise results.
It is just the notation when I am writing the code.
I write in lower case letters:
If getdate(myString) = True Then myDate = getdatevalue
and expect that VBA corrects the notation as it is defined in the .XLAM module and VBA does with all other code:
If getDate(myString) = True Then myDate = getDateValue
VBA underlying application will normally standardize declared variables and function names, I am no expert on how the logic is applied, but I would assume that it would look in .xlam modules for reference functions and macro names when they are used in .xlsm workbooks. So I cannot explain why that particular code is giving you a problem. I have tried to duplicate it and cannot. Mine all changes to the same case throughout, Based on what the original usage or declaration was. Is it possible that you have anoter macro or function in the .xlam file that uses the same variables but with the upper case letters? (although, I don't see how that could be, based on the application standard). Big mystery!
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks