Access 2007 - Help

G

Gary S

I just read an article called 10+ Reasons to
use Access. A couple of things it said surprised
me.

Like, Access 2007 does not support run time.
Also it said Access 2007 'security model...
does not exist at all in Access 2007'.

Also heard from a different source that Access
2007 is designed to run macros and VBA has
been dowgraded in some shape or form.

Could someone in the know talk to these
items?
 
A

Allen Browne

Responses in-line.

Gary S said:
I just read an article ...

Like, Access 2007 does not support run time.
Click to expand...

False.

Microsoft provides a *free* runtime for A2007.
That's never happened in any previous version.
Details:
http://www.microsoft.com/downloads/...D9-9DC6-4B38-9FA6-2C745A175AED&displaylang=en
Also it said Access 2007 'security model...
does not exist at all in Access 2007'.
Click to expand...

Partially true.

Although A2007 does respect the security for the older MDB format, it does
not for the new ACCDB format.

If you really need a secure database, you should not be using Access anyway.
Also heard from a different source that Access
2007 is designed to run macros and VBA has
been dowgraded in some shape or form.
Click to expand...

False.

Access 2007 certainly did enhance macros, but it did not downgrade VBA.
Could someone in the know talk to these
items?
Click to expand...

Here's some more info on A2007, designed for people familiar with the
previous versions:
http://allenbrowne.com/Access2007.html
 
D

DaveT

"If you really need a secure database, you should not be using Access anyway."

I disagree. Most workgroups (small business, corp dept) are not keeping
state secrets. However, they would like something to keep well-intended
people from doing untended things. And they do grasp the concept of user
groups (for example those who edit data v. those who read data, run reports,
etc) and would like this supported.

Also, while one can either user Win API's to grab workstation info, or dummy
up some artificial logon process, most groups undertand the concept of user
names and passwords and the idea of both tracking who does what along with
who is logged on (even displaying username on titlebars and the like).

The argument that a motivated hacker can "hack" workgroups security distorts
entirely the utility of workgroup security. Of course mdw files can be
hacked; what's new? Show me somehting that can't be hacked.

The notion of only real men use SQL flies in the face of reality. Most small
buinsesses do not have IT staffs and cannot manage the complexities of SQL
Server.

At the department level, groups want Access for the very reason that IT has
a stranglehold on SQL applications and development.

I think Micorsoft erred in removing workgroup security in Access 2007 and
the suggested workarounds are weak contortions.
 
Top