|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Programically redirecting to different mdw filesi work with a lot of Access applications and they all have different users
and security files. Instead of having to always join a new security file whenever I am working on a new database how would I programically point to the mdw file for the particular application? Use a shortcut that points to the appropriate .mdw file. The general syntax
is: FullPathToMSAccess.exe FullPathToDatabase.mdb /wrkgrp FullPathToWIF.mdw Show quoteHide quote "Cameron" <Came***@discussions.microsoft.com> wrote in message news:23A49745-FE6D-4EDD-A36D-90B4F69D1B6E@microsoft.com... >i work with a lot of Access applications and they all have different users > and security files. Instead of having to always join a new security file > whenever I am working on a new database how would I programically point to > the mdw file for the particular application? Cool, that looks rather easy to do. So I am just passing the MDW file to
Access then. Show quoteHide quote "Lynn Trapp" wrote: > Use a shortcut that points to the appropriate .mdw file. The general syntax > is: > > FullPathToMSAccess.exe FullPathToDatabase.mdb /wrkgrp FullPathToWIF.mdw > > -- > > Lynn Trapp > Microsoft MVP (Access) > www.ltcomputerdesigns.com > > > "Cameron" <Came***@discussions.microsoft.com> wrote in message > news:23A49745-FE6D-4EDD-A36D-90B4F69D1B6E@microsoft.com... > >i work with a lot of Access applications and they all have different users > > and security files. Instead of having to always join a new security file > > whenever I am working on a new database how would I programically point to > > the mdw file for the particular application? > > > Yes, and you need to be sure that all the users are joined to the default
..mdw file that ships with access. Show quoteHide quote "Cameron" <Came***@discussions.microsoft.com> wrote in message news:E6319F2F-623D-42F1-B592-21B5BAE5E679@microsoft.com... > Cool, that looks rather easy to do. So I am just passing the MDW file to > Access then. > > "Lynn Trapp" wrote: > >> Use a shortcut that points to the appropriate .mdw file. The general >> syntax >> is: >> >> FullPathToMSAccess.exe FullPathToDatabase.mdb /wrkgrp FullPathToWIF.mdw >> >> -- >> >> Lynn Trapp >> Microsoft MVP (Access) >> www.ltcomputerdesigns.com >> >> >> "Cameron" <Came***@discussions.microsoft.com> wrote in message >> news:23A49745-FE6D-4EDD-A36D-90B4F69D1B6E@microsoft.com... >> >i work with a lot of Access applications and they all have different >> >users >> > and security files. Instead of having to always join a new security >> > file >> > whenever I am working on a new database how would I programically point >> > to >> > the mdw file for the particular application? >> >> >> Oh, I think that should be the case. When the clients on the network get
imaged they are generally built as per default install. Show quoteHide quote "Lynn Trapp" wrote: > Yes, and you need to be sure that all the users are joined to the default > ..mdw file that ships with access. > > -- > > Lynn Trapp > Microsoft MVP (Access) > www.ltcomputerdesigns.com > > > "Cameron" <Came***@discussions.microsoft.com> wrote in message > news:E6319F2F-623D-42F1-B592-21B5BAE5E679@microsoft.com... > > Cool, that looks rather easy to do. So I am just passing the MDW file to > > Access then. > > > > "Lynn Trapp" wrote: > > > >> Use a shortcut that points to the appropriate .mdw file. The general > >> syntax > >> is: > >> > >> FullPathToMSAccess.exe FullPathToDatabase.mdb /wrkgrp FullPathToWIF.mdw > >> > >> -- > >> > >> Lynn Trapp > >> Microsoft MVP (Access) > >> www.ltcomputerdesigns.com > >> > >> > >> "Cameron" <Came***@discussions.microsoft.com> wrote in message > >> news:23A49745-FE6D-4EDD-A36D-90B4F69D1B6E@microsoft.com... > >> >i work with a lot of Access applications and they all have different > >> >users > >> > and security files. Instead of having to always join a new security > >> > file > >> > whenever I am working on a new database how would I programically point > >> > to > >> > the mdw file for the particular application? > >> > >> > >> > > > Will this shortcut work with mde databases also?
I have taken over a position to work on and deploy a database to several locations within the organization. I currently have a new deployment that is giving trouble. I built a shortcut like you had mentioned to open the freshly deployed DB but when the user opens it for the first time it starts to open and then Poof closes. I have seen this before when I have not been pointed or entered into the mdw file but I don't get it the shortcut should work. Any thoughts? Show quoteHide quote "Lynn Trapp" wrote: > Yes, and you need to be sure that all the users are joined to the default > ..mdw file that ships with access. > > -- > > Lynn Trapp > Microsoft MVP (Access) > www.ltcomputerdesigns.com > > > "Cameron" <Came***@discussions.microsoft.com> wrote in message > news:E6319F2F-623D-42F1-B592-21B5BAE5E679@microsoft.com... > > Cool, that looks rather easy to do. So I am just passing the MDW file to > > Access then. > > > > "Lynn Trapp" wrote: > > > >> Use a shortcut that points to the appropriate .mdw file. The general > >> syntax > >> is: > >> > >> FullPathToMSAccess.exe FullPathToDatabase.mdb /wrkgrp FullPathToWIF.mdw > >> > >> -- > >> > >> Lynn Trapp > >> Microsoft MVP (Access) > >> www.ltcomputerdesigns.com > >> > >> > >> "Cameron" <Came***@discussions.microsoft.com> wrote in message > >> news:23A49745-FE6D-4EDD-A36D-90B4F69D1B6E@microsoft.com... > >> >i work with a lot of Access applications and they all have different > >> >users > >> > and security files. Instead of having to always join a new security > >> > file > >> > whenever I am working on a new database how would I programically point > >> > to > >> > the mdw file for the particular application? > >> > >> > >> > > > It should werk fine with .mde files. I'm not sure about your problem with it
shutting down without warning. Show quoteHide quote "Cameron" <Came***@discussions.microsoft.com> wrote in message news:8A258830-4237-4E68-A015-61890CB66690@microsoft.com... > Will this shortcut work with mde databases also? > > I have taken over a position to work on and deploy a database to several > locations within the organization. I currently have a new deployment that > is > giving trouble. I built a shortcut like you had mentioned to open the > freshly > deployed DB but when the user opens it for the first time it starts to > open > and then Poof closes. I have seen this before when I have not been pointed > or > entered into the mdw file but I don't get it the shortcut should work. Any > thoughts? > > "Lynn Trapp" wrote: > >> Yes, and you need to be sure that all the users are joined to the default >> ..mdw file that ships with access. >> >> -- >> >> Lynn Trapp >> Microsoft MVP (Access) >> www.ltcomputerdesigns.com >> >> >> "Cameron" <Came***@discussions.microsoft.com> wrote in message >> news:E6319F2F-623D-42F1-B592-21B5BAE5E679@microsoft.com... >> > Cool, that looks rather easy to do. So I am just passing the MDW file >> > to >> > Access then. >> > >> > "Lynn Trapp" wrote: >> > >> >> Use a shortcut that points to the appropriate .mdw file. The general >> >> syntax >> >> is: >> >> >> >> FullPathToMSAccess.exe FullPathToDatabase.mdb /wrkgrp >> >> FullPathToWIF.mdw >> >> >> >> -- >> >> >> >> Lynn Trapp >> >> Microsoft MVP (Access) >> >> www.ltcomputerdesigns.com >> >> >> >> >> >> "Cameron" <Came***@discussions.microsoft.com> wrote in message >> >> news:23A49745-FE6D-4EDD-A36D-90B4F69D1B6E@microsoft.com... >> >> >i work with a lot of Access applications and they all have different >> >> >users >> >> > and security files. Instead of having to always join a new security >> >> > file >> >> > whenever I am working on a new database how would I programically >> >> > point >> >> > to >> >> > the mdw file for the particular application? >> >> >> >> >> >> >> >> >> It will also work with mde files.
If any paths have spaces in them you must enclose the entire path in double quotes. If you still have trouble, post back with what you have in the target of the shortcut. -- Show quoteHide quoteJoan Wild Microsoft Access MVP Cameron wrote: > Will this shortcut work with mde databases also? > > I have taken over a position to work on and deploy a database to > several locations within the organization. I currently have a new > deployment that is giving trouble. I built a shortcut like you had > mentioned to open the freshly deployed DB but when the user opens it > for the first time it starts to open and then Poof closes. I have > seen this before when I have not been pointed or entered into the mdw > file but I don't get it the shortcut should work. Any thoughts? > > "Lynn Trapp" wrote: > >> Yes, and you need to be sure that all the users are joined to the >> default ..mdw file that ships with access. >> >> -- >> >> Lynn Trapp >> Microsoft MVP (Access) >> www.ltcomputerdesigns.com >> >> >> "Cameron" <Came***@discussions.microsoft.com> wrote in message >> news:E6319F2F-623D-42F1-B592-21B5BAE5E679@microsoft.com... >>> Cool, that looks rather easy to do. So I am just passing the MDW >>> file to Access then. >>> >>> "Lynn Trapp" wrote: >>> >>>> Use a shortcut that points to the appropriate .mdw file. The >>>> general syntax >>>> is: >>>> >>>> FullPathToMSAccess.exe FullPathToDatabase.mdb /wrkgrp >>>> FullPathToWIF.mdw >>>> >>>> -- >>>> >>>> Lynn Trapp >>>> Microsoft MVP (Access) >>>> www.ltcomputerdesigns.com >>>> >>>> >>>> "Cameron" <Came***@discussions.microsoft.com> wrote in message >>>> news:23A49745-FE6D-4EDD-A36D-90B4F69D1B6E@microsoft.com... >>>>> i work with a lot of Access applications and they all have >>>>> different users >>>>> and security files. Instead of having to always join a new >>>>> security file >>>>> whenever I am working on a new database how would I programically >>>>> point to >>>>> the mdw file for the particular application? 
Other interesting topics
User level security-- do not have necessary permissions
restrict combo box selection depending on user mapped network drive and security error Tab Change Passwords Password for opening Report user without admin privilleges was able to join his computer to do Secure back end database Open an Access Database from Another UnHIDE a tbl look for VBA codes to make Tables and Quries to be READ ONLY |
|||||||||||||||||||||||
