By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,850 Members | 967 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,850 IT Pros & Developers. It's quick & easy.

Package and deployment and MDE

P: n/a
I made my database an MDE and I still have access to all the forms, tables
etc. I was trying to do the package and deployment now to see if that would
help. But it is not in the Add-In manager and I don't know how or where to
find it. Can anyone help me out this would be greatly appreciated. I'm Using
Office Professional.

Thanks in Advance
SPMU
Nov 12 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
"SPMU" <sp**@hotmail.com> wrote in message
news:%q**********************@ursa-nb00s0.nbnet.nb.ca...
I made my database an MDE and I still have access to all the forms, tables
etc. I was trying to do the package and deployment now to see if that would
help. But it is not in the Add-In manager and I don't know how or where to
find it. Can anyone help me out this would be greatly appreciated. I'm Using
Office Professional.


Making an MDE version of your file only prevents *design changes* to code-based
objects (forms, reports, modules). It in no way changes the interface or makes
the file act any differently. If you want to hide or obscure the db window or
the normal Access interface that is an entirely different subject that has
little to do with converting to an MDE. Most of those are found in the Startup
menu and if you do a Google search on the topic you will find a few other things
you can do including implementing Access user-level security (a bit of an
advanced topic).
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 12 '05 #2

P: n/a
If you want a bulletproof deployment of an access application check out
www.sagekey.com the make install scripts that make your install independent
of other installation of office.

I use them all the time and they are quick and reliable.

Seth B Spearman
"SPMU" <sp**@hotmail.com> wrote in message
news:%q**********************@ursa-nb00s0.nbnet.nb.ca...
I made my database an MDE and I still have access to all the forms, tables
etc. I was trying to do the package and deployment now to see if that would help. But it is not in the Add-In manager and I don't know how or where to
find it. Can anyone help me out this would be greatly appreciated. I'm Using Office Professional.

Thanks in Advance
SPMU

Nov 12 '05 #3

P: n/a
But I have changed a db to mde before and the tables were not accessible to
the user only to the developer, but this time it is allowing anyone access
to the tables, queries etc.

Do you know anything about getting an add-in to appear in the VB editor
add-ins?
"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:c2*************@ID-98015.news.uni-berlin.de...
"SPMU" <sp**@hotmail.com> wrote in message
news:%q**********************@ursa-nb00s0.nbnet.nb.ca...
I made my database an MDE and I still have access to all the forms, tables
etc. I was trying to do the package and deployment now to see if that would help. But it is not in the Add-In manager and I don't know how or where to
find it. Can anyone help me out this would be greatly appreciated. I'm Using Office Professional.


Making an MDE version of your file only prevents *design changes* to
code-based
objects (forms, reports, modules). It in no way changes the interface or
makes
the file act any differently. If you want to hide or obscure the db window
or
the normal Access interface that is an entirely different subject that has
little to do with converting to an MDE. Most of those are found in the
Startup
menu and if you do a Google search on the topic you will find a few other
things
you can do including implementing Access user-level security (a bit of an
advanced topic).
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com


Nov 12 '05 #4

P: n/a
"SPMU" <sp**@hotmail.com> wrote in message
news:ur**********************@ursa-nb00s0.nbnet.nb.ca...
But I have changed a db to mde before and the tables were not accessible to
the user only to the developer, but this time it is allowing anyone access
to the tables, queries etc.
Sorry, but you're mistaken. There are ways to make the tables "difficult" to
access. Using an MDE is not one of them. If you deploy your app using the
Runtime on a PC that has no other verson of Access on it then the user will not
have direct access to the db window. However; that is a limitation of the
Runtime environment, not of an MDE.
Do you know anything about getting an add-in to appear in the VB editor
add-ins?


Sorry, no.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 12 '05 #5

P: n/a
"SPMU" <sp**@hotmail.com> wrote:
Do you know anything about getting an add-in to appear in the VB editor
add-ins?


Usysreginfo is the key word to search on if memory serves me.

Yup, it is. USysRegInfo Table Format.

See my Add-in Tips, Hints and Gotchas page at
http://www.granite.ab.ca/access/addins.htm for a few links on these although I wasn't
concentrating on usysreginfo.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Nov 12 '05 #6

P: n/a

"Rick Brandt" <ri*********@hotmail.com> wrote in message
news:c2*************@ID-98015.news.uni-berlin.de...
"SPMU" <sp**@hotmail.com> wrote in message
news:ur**********************@ursa-nb00s0.nbnet.nb.ca...
But I have changed a db to mde before and the tables were not accessible to the user only to the developer, but this time it is allowing anyone access
to the tables, queries etc.


Sorry, but you're mistaken. There are ways to make the tables "difficult"
to
access. Using an MDE is not one of them. If you deploy your app using the
Runtime on a PC that has no other verson of Access on it then the user will
not
have direct access to the db window. However; that is a limitation of the
Runtime environment, not of an MDE.
Yes, you are right, I guess I had a bit of brain freeze last night, Thanks
for your help. It is much appreciated. Thanks.


Nov 12 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.