This line, [vba]WbTGSU.Close savechanges:=True[/vba]
I expected to change to [vba]SaveChanges:=True[/vba], for the syntax to shift VBA terms to uppercase. Am I mistaken about this?
It shows it w/ uppercase in the help files.
This line, [vba]WbTGSU.Close savechanges:=True[/vba]
I expected to change to [vba]SaveChanges:=True[/vba], for the syntax to shift VBA terms to uppercase. Am I mistaken about this?
It shows it w/ uppercase in the help files.
my site: www.ecboardco.com
was built w/ a majority of the assistance from the board members here... thanks VBAX.
Just because I see something, doesn't mean that what's actually happening is what I see.
You don't get from 0-90 by standing still!
I get the same behaviour.
MVP (Excel 2008-2010)
Post a workbook with sample data and layout if you want a quicker solution.
To help indent your macros try Smart Indent
Please remember to mark threads 'Solved'
Well, I am in good company then. I will leave it open for now to see if anyone else knows anything about this.
my site: www.ecboardco.com
was built w/ a majority of the assistance from the board members here... thanks VBAX.
Just because I see something, doesn't mean that what's actually happening is what I see.
You don't get from 0-90 by standing still!
I also get it, have gotten it for a long time (probably always), and get it on other things, I just never thought to question it.
____________________________________________
Nihil simul inventum est et perfectum
Abusus non tollit usum
Last night I dreamed of a small consolation enjoyed only by the blind: Nobody knows the trouble I've not seen!
James Thurber
Thanks you guys for confirming that. Bob as you have pointed out about writing in lowercase to catch potential errors I do try to stick to this policy.
regards....
my site: www.ecboardco.com
was built w/ a majority of the assistance from the board members here... thanks VBAX.
Just because I see something, doesn't mean that what's actually happening is what I see.
You don't get from 0-90 by standing still!