--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com ch...@cpearson.com
"mates" <matej....@nospam-ibisco.si> wrote in message
news:#MZE8B2wAHA.632@tkmsftngp03...
One thing to be aware of is a new setting called 'Trust access to Visual
Basic project.' This setting is turned off, by default. When it's turned
off, your VBA code cannot manipulate objects in the VB Project. In Excel
2002, the example at my web site won't work unless the user changes the
default setting:
http://j-walk.com/ss/excel/tips/tip76.htm
Also custom toolbars and toolbar customizations created in previous versions
are not migrated to Excel 2002. And if you happen to use Microsoft Map,
you'll find that it has been removed from Excel 2002.
You might want to take a look at MS's Knowledge Base:
http://search.support.microsoft.com/kb/
Do a search for Excel 2002, and check for what's new within the past 30
days.
John Walkenbach
For Excel tips, macros, & downloads...
http://j-walk.com/ss
"mates" <matej....@nospam-ibisco.si> wrote in message
news:#MZE8B2wAHA.632@tkmsftngp03...
Regards,
Niek Otten
"mates" <matej....@nospam-ibisco.si> wrote in message
news:#MZE8B2wAHA.632@tkmsftngp03...
> Latest reviews don't say much about changes in VBA, object model, Forms, ...
> is there something a serious developer should be aware of?
Contrary to Chip and John, I think there's actually quite a few minor, but
useful, changes to the Excel object model, particularly for the serious
developer, including:
The Application object getting hWnd and hDC values, to use in our API calls
CommandBar buttons now have a Picture property that can be set and read,
meaning the end of PasteFace and wiping the clipboard.
We can override the system default regional settings, for example to print
reports for different countries.
The formula auditing function is very useful when you're trying to work out
what a formula is doing (particularly if you're reviewing/redesigning somebody
else's worksheet!)
We can now completely prevent the ability for users to customize our
commandbars if we want to
We can password protect individual ranges within a sheet, and specify who
that protection applies to.
When protecting sheets, there is much more control of what can/can't be done
by the user in the sheet
The Function tooltips are extremely useful - when entering a function in the
worksheet, the parameters pop up, just like they do in the VBE.
When saving a workbook, we can choose which encryption algorithm to use, from
those available to windows, providing 'bullet-proof' workbook security
Individual workbooks can now be signed using a digital signature. If the
file is altered and saved, the signatures are removed. This provides an
excellent mechanism for 'approval' processes, as well as confirmation that
files we created haven't been tampered with since their creation. (In Excel
2000, you could do that to the VB projects. Excel 2002 applies the same
principle to the entire workbook).
Regards
Stephen Bullen
Microsoft MVP - Excel
http://www.BMSLtd.co.uk or http://208.49.24.208
What does "specify who that protection applies to" mean ? Can I lock it from
the four untrusted fools and let the rest have more freedom ?
Also, are there more events than before ?
Best wishes Harald
Stephen Bullen <Ste...@BMSLtd.ie> wrote in message
news:VA.0000082...@bmsltd.ie...
What will happen when workbooks with advanced protection are opened in XL
97/2000? Is my assumption that the cells will be locked for all users
correct? If a wb created with XP is opened saved from 97/2000, will the
advanced protection (and/or other XP features) still be present when opened
back in XP, or will non-97/2000 functionality be gone?
Can anyone that has been using XP predict any dramatic/problematic issues
when moving a workbook from an XP machine back to a 97/2000 machine?
I'm would love to demo XP myself, but can't because I don't have a spare
machine, and can't risk tampering with my current machine at this time.
Hopefully I will have a chance to test XP soon, as I'm the guy at my company
who usually deals with MSOffice version migration issues.
Thanks,
--
Jeff McAhren
Dallas, Texas
"Stephen Bullen" <Ste...@BMSLtd.ie> wrote in message
news:VA.0000082...@bmsltd.ie...
XL2002: Summary of Workbook and Worksheet Application Events
http://support.microsoft.com/support/kb/articles/Q291/2/94.ASP
"Harald Staff" <harald...@eunet.no> wrote in message
news:uatba05wAHA.2292@tkmsftngp02...
> Wow. Lots of pretty cool things :-)
>
<snip>
Tim
"John Walkenbach" <jo...@j-walk.com> wrote in message
...
Best wishes Harald
Dana DeLouis <da...@email.msn.com> wrote in message
news:OIivG66wAHA.1392@tkmsftngp03...
> What will happen when workbooks with advanced protection are opened in XL
> 97/2000? Is my assumption that the cells will be locked for all users
> correct?
Yes.
> If a wb created with XP is opened saved from 97/2000, will the
> advanced protection (and/or other XP features) still be present when opened
> back in XP, or will non-97/2000 functionality be gone?
I just tested this:
1. Started Excel 2002, set range A1:F15 of sheet1 to be editable by myself
without a password, and by everyone else with a password. Save and close the
file.
2. Started Excel 97, open the same file. All cells are locked and can't be
edited. Changed some stuff in Sheet2. Unprotected Sheet1, changed some
stuff, protected it again. Saved and closed the file
3. Opened it again in Excel 2002, and the protection that I set up in step 1
was still there and working.
> What does "specify who that protection applies to" mean ? Can I lock it from
> the four untrusted fools and let the rest have more freedom ?
Exactly that. I'm not sure if it requires specific a O/S though <g>.
--
Jeff McAhren
Dallas, Texas
"Stephen Bullen" <Ste...@BMSLtd.ie> wrote in message
news:VA.0000082...@bmsltd.ie...