MDE & 2003

[Tim Marshall]

My A2003 is set up so that the default file format is Access 2000
(options, advanced tab). I've just tried to make my first A2003 mdb
into an mde and I get an error saying: "you cannot create a <mdb name>
ADE or MDE from a dtabase saved in <mdb name> 2000 format."

Also, in help there's a curious note I simply don't understand which
I've reproduced below (help on mde, "About ADE & MDE files").

I'm a former A97 developer, can someone please explain this to me in
terms an idiot might understand? I'd really appreciate it or a pointer
to previous discussions on this issue here.

Thanks very much in advance - quote from help follows:

"Code no longer employs user-level security

"In previous versions of Access, user-level security could be used with
VBA modules. In Microsoft Access 2000 and later, all Visual Basic code
for an Access database (.mdb) file or an Access project (.adp)
(Microsoft Access project: An Access file that connects to a Microsoft
SQL Server database and is used to create client/server applications. A
project file doesn't contain any data or data-definition-based objects
such as tables and views.) file, including stand-alone modules (standard
module: A module in which you can place Sub and Function procedures that
you want to be available to other procedures throughout your database.)
and class modules (class module: A module that can contain the
definition for a new object. Each instance of a class creates a new
object. Procedures defined in the module become properties and methods
of the object. Class modules can exist alone or with forms and reports.)
(such as code behind forms and reports), must employ security
technologies, such as setting a password, or by saving the database as
an MDE or ADE file, which removes the source code."

--
Tim
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

[Steve Jorgensen]

On Thu, 28 Oct 2004 10:18:45 -0230, Tim Marshall <TI****@antarctic.flowerpots>
wrote:

My A2003 is set up so that the default file format is Access 2000
(options, advanced tab). I've just tried to make my first A2003 mdb
into an mde and I get an error saying: "you cannot create a <mdb name>
ADE or MDE from a dtabase saved in <mdb name> 2000 format."
I think you just have to convert the file to Access 2003 format, compile the
code, then create the MDE file from that.
Also, in help there's a curious note I simply don't understand which
I've reproduced below (help on mde, "About ADE & MDE files").

I'm a former A97 developer, can someone please explain this to me in
terms an idiot might understand? I'd really appreciate it or a pointer
to previous discussions on this issue here.

Thanks very much in advance - quote from help follows:

"Code no longer employs user-level security

"In previous versions of Access, user-level security could be used with
VBA modules. In Microsoft Access 2000 and later, all Visual Basic code
for an Access database (.mdb) file or an Access project (.adp)
(Microsoft Access project: An Access file that connects to a Microsoft
SQL Server database and is used to create client/server applications. A
project file doesn't contain any data or data-definition-based objects
such as tables and views.) file, including stand-alone modules (standard
module: A module in which you can place Sub and Function procedures that
you want to be available to other procedures throughout your database.)
and class modules (class module: A module that can contain the
definition for a new object. Each instance of a class creates a new
object. Procedures defined in the module become properties and methods
of the object. Class modules can exist alone or with forms and reports.)
(such as code behind forms and reports), must employ security
technologies, such as setting a password, or by saving the database as
an MDE or ADE file, which removes the source code."

Basically, VBA code is now treated more like it is in other Office documents,
and is no longer as much the purvue of Access itself. Since the VB IDE is not
hooked in to the Access user-level security system, security for code no
longer works the same way. Your options now are that you can either protect
the code project as a whole by setting a password for the project, or you can
create an MDE which contains only the compiled code, not the original code
text.

[Tim Marshall]

Steve Jorgensen wrote:

I think you just have to convert the file to Access 2003 format, compile the
code, then create the MDE file from that.

Thanks, Steve, for this and the explanation of security & modules.
--
Tim
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto

[david epsom dot com dot au]

If you double click or open a Module in the Access Database
Window, Access checks the security settings for that module
before opening the module in the VBA window.

But in the VBA window, you can open any of the code modules
from the VBA project window, without regard to the Access
security settings.

So the Security form in Access no longer displays the Access
security settings for code modules. You can still set them
in code, and they still apply when in Access, but the VBA IDE
ignores them.

(david)
"Steve Jorgensen" <no****@nospam.nospam> wrote in message
news:17********************************@4ax.com...

On Thu, 28 Oct 2004 10:18:45 -0230, Tim Marshall <TI****@antarctic.flowerpots> wrote:

My A2003 is set up so that the default file format is Access 2000
(options, advanced tab). I've just tried to make my first A2003 mdb
into an mde and I get an error saying: "you cannot create a <mdb name>
ADE or MDE from a dtabase saved in <mdb name> 2000 format."
I think you just have to convert the file to Access 2003 format, compile

the code, then create the MDE file from that.

Also, in help there's a curious note I simply don't understand which
I've reproduced below (help on mde, "About ADE & MDE files").

I'm a former A97 developer, can someone please explain this to me in
terms an idiot might understand? I'd really appreciate it or a pointer
to previous discussions on this issue here.

Thanks very much in advance - quote from help follows:

"Code no longer employs user-level security

"In previous versions of Access, user-level security could be used with
VBA modules. In Microsoft Access 2000 and later, all Visual Basic code
for an Access database (.mdb) file or an Access project (.adp)
(Microsoft Access project: An Access file that connects to a Microsoft
SQL Server database and is used to create client/server applications. A
project file doesn't contain any data or data-definition-based objects
such as tables and views.) file, including stand-alone modules (standard
module: A module in which you can place Sub and Function procedures that
you want to be available to other procedures throughout your database.)
and class modules (class module: A module that can contain the
definition for a new object. Each instance of a class creates a new
object. Procedures defined in the module become properties and methods
of the object. Class modules can exist alone or with forms and reports.)
(such as code behind forms and reports), must employ security
technologies, such as setting a password, or by saving the database as
an MDE or ADE file, which removes the source code."
Basically, VBA code is now treated more like it is in other Office

documents, and is no longer as much the purvue of Access itself. Since the VB IDE is not hooked in to the Access user-level security system, security for code no
longer works the same way. Your options now are that you can either protect the code project as a whole by setting a password for the project, or you can create an MDE which contains only the compiled code, not the original code
text.