E
Ed
Hello!
1.
I have created an MDE file and have disabled all the menus, standard
toolbars, shortcut keys, etc. The MDE is a front-end to a secured
back-end database. The person who will use the MDE needs to be able to
change his/her password and holding shift at the password prompt is
too complicated for them. Is there any way to access the "change
password" window from VBA or macro. I want to remind you that I have
disabled full menus from the start-up options. The database is in
Access2002.
2.
For my second question on the same project: Both the front-end and the
back-end are on a shared network drive and the person will access them
from his workstation with a shortcut. ex:
\\server\sharedfolder\database.mdb /wrkgrp
\\server\sharedfolder\users.mdw /user user_name
I could give the person the front-end to be used locally but by
keeping all files on the network drive, there is only one place, only
one version to change, etc. The network is pretty fast and I have not
noticed any advantages to using a local front-end. Is this
recommended? Any advantages to using local front-ends?
3.
I just thought of another question: How can I force exclusive access
to the back end database? I have read something about exclusive linked
tables but I am not sure how to accomplish this. If I put /excl in the
shortcut for the front-end that only opens the front-end exclusively
and not the back-end, right?
Sorry for the multiple questions. Thanks to you guys and to google
newsgroups I keep getting better every day.
Ed
1.
I have created an MDE file and have disabled all the menus, standard
toolbars, shortcut keys, etc. The MDE is a front-end to a secured
back-end database. The person who will use the MDE needs to be able to
change his/her password and holding shift at the password prompt is
too complicated for them. Is there any way to access the "change
password" window from VBA or macro. I want to remind you that I have
disabled full menus from the start-up options. The database is in
Access2002.
2.
For my second question on the same project: Both the front-end and the
back-end are on a shared network drive and the person will access them
from his workstation with a shortcut. ex:
\\server\sharedfolder\database.mdb /wrkgrp
\\server\sharedfolder\users.mdw /user user_name
I could give the person the front-end to be used locally but by
keeping all files on the network drive, there is only one place, only
one version to change, etc. The network is pretty fast and I have not
noticed any advantages to using a local front-end. Is this
recommended? Any advantages to using local front-ends?
3.
I just thought of another question: How can I force exclusive access
to the back end database? I have read something about exclusive linked
tables but I am not sure how to accomplish this. If I put /excl in the
shortcut for the front-end that only opens the front-end exclusively
and not the back-end, right?
Sorry for the multiple questions. Thanks to you guys and to google
newsgroups I keep getting better every day.
Ed