![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
I use that feature myself. Sometimes, I even remember to hit Ctrl+<space> before I've typed AllThatLongVariableName and let intellisense plug the name in for me (of course, I type it as allthatlongvariablename). |
#12
| |||
| |||
|
|
The default, since the beginning of Access / and classic VB has always been "variant" and each variable name without its own "AS clause" has defaulted to "variant". |
#13
| |||
| |||
|
|
"Access Developer" <accdevel (AT) gmail (DOT) com> wrote in news:8pp0ptF6ecU1 (AT) mid (DOT) individual.net: The default, since the beginning of Access / and classic VB has always been "variant" and each variable name without its own "AS clause" has defaulted to "variant". I never did it wrong, because I never declare multiple variables on one line (it's too hard to read), but I could swear I'd seen sample code that used it. But in going through all the code I have, I don't see any of it doing it wrong. I guess I must misperceived what was being suggested -- I'm glad I didn't like it, or I would have written a lot of bad code over the years (though surely I would have realized there were problems the first time I assumed an unitialized variable was a 0 and it turned out to be empty). -- David W. Fenton http://www.dfenton.com/ contact via website only http://www.dfenton.com/DFA/ |
#14
| |||
| |||
|
|
As someone pointed out, it works in compilers for some other languages -- perhaps that's where you saw it. I'm thinking that maybe it even worked in Borland Turbo Basic, but it's been a long time since I used that one. |
|
Larry "David-W-Fenton" <dfassoc (AT) dfenton (DOT) com> wrote in message news:Xns9E73AEEE471BBf99a49ed1d0c49c5bbb2 (AT) 74 (DOT) 209.136.97... "Access Developer" <accdevel (AT) gmail (DOT) com> wrote in news:8pp0ptF6ecU1 (AT) mid (DOT) individual.net: The default, since the beginning of Access / and classic VB has always been "variant" and each variable name without its own "AS clause" has defaulted to "variant". I never did it wrong, because I never declare multiple variables on one line (it's too hard to read), but I could swear I'd seen sample code that used it. But in going through all the code I have, I don't see any of it doing it wrong. I guess I must misperceived what was being suggested -- I'm glad I didn't like it, or I would have written a lot of bad code over the years (though surely I would have realized there were problems the first time I assumed an unitialized variable was a 0 and it turned out to be empty). -- David W. Fenton http://www.dfenton.com/ contact via website only http://www.dfenton.com/DFA/ |
#15
| |||
| |||
|
|
As someone pointed out, it works in compilers for some other languages -- perhaps that's where you saw it. |
|
I'm thinking that maybe it even worked in Borland Turbo Basic, but it's been a long time since I used that one. |
![]() |
| Thread Tools | |
| Display Modes | |
| |