[AccessD] Macros A Rant???

Martin,

Thank you for clueing us in on what is going on in the background
between Access MVPs and M$ on this subject.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us


-----Original Message-----
From: Mwp.Reid at Queens-Belfast.AC.UK
[mailto:Mwp.Reid at Queens-Belfast.AC.UK] 
Sent: Friday 2003 Apr 25 08:44
To: accessd at databaseadvisors.com
Subject: [AccessD] Macros A Rant???

For what its worth

Personally I think you are incorrect. This discussion has also been
carried on 
a MIcrosoft Beta Newgroup restricted to Access MVPs plus a few others.
The 
reason being that MS is referring to everything in Access as a Macro
Project 
including VBA. When you work with the new security features of Access
2003 you 
set them under the tools macro security option. However the effects
apply 
equally to VBA, SQL Queries (action Queries) etc. This came about as a
direct 
result of Microsoft viewing Access Macros as on par wth those of WOrd
and 
Excel which we are arguing with MS is not the case. For example when you
oepn 
Access 2003 you get ht witha MAcro warning. If you choose to disable
Macros 
youa re in fact stopping VBA from being loaded. i.e you code driven
database 
falls apart.

So while some of you find it boring it will in fact have a fairly large
impact 
of how you work with security in Access 2003 and beyond mainly due to
the 
confusion over Macros and VBA. 

SO in fact its not a rant. Its just happens that a very serious
discussion 
between developers with Microsoft was matched by a similar discussion on

AccessD.

Thats my thinking anyway

Martin