quote:Originally posted by mschenk
although the code worked even with spaces in the form and report names, there must be times when spaces cause problems. What sort of problems do they cause?
Well, not so much problems as inconveniences.
Over the years, Microsoft has tried to make its software "idiot proof" by providing automatic responses to typewritten text. Sometimes it works, and other times not. For example, you're in Word and that annoying paper clip appears when it thinks it's trying to be helpful and usually it's not
. One good
thing Access does is that when you type VBA code, properties and collections of control objects autofinish when you type.
So if you're coding something for a textbox, for example, if your textbox is named "My Text Box" then you'll always have to type Me.[My Text Box].This or Me.[My Text Box].That; however, not so if you name it something like "txtMyTextBox". In this instance, as soon as you type "Me.txt", Access will list out all of your control objects. Continue typing "Me.txtMy" and sure enough "Me.txtMyTextBox" will appear and you just press space and keep going. This is very handy and speeds you up a great deal.
Naming conventions for objects are "txt
MyOptionGroup", etc. In that way, when the autofill kicks in, like objects are alphabetized and grouped together for easy retrieval.
Note: the bang (!) doesn't invoke this autofill and so the period is used all the time now. The bang is becoming obsolete.
quote:Secondly, do I need to load all the DAO libraries or just the latest one (I think it is version 3.6)?
I only load the latest one.
Michigan Dept. of Environmental Quality, Air Quality Division