Nicholson, Karen
cyx5 at cdc.gov
Thu Nov 4 14:15:56 CST 2004
Not so lucky; the .mdw is on the workstations, buried. Life is getting easier, though. I have the front end updater working and it is like a birthday party for them! -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mackin, Christopher Sent: Thursday, November 04, 2004 1:49 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] MDW ByPass Surgery, Post Op Alternatively, if you have a large group of users pointing to a particular .mdw on the network you can simply archive the current .mdw and copy your system.mdw into the network folder and rename it to match the currently used one. That saves having to rejoin workgroups and leaves you with the option of reverting to the old security by just replacing the file. -Chris Mackin -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Heenan, Lambert Sent: Thursday, November 04, 2004 11:09 AM To: 'Access Developers discussion and problem solving'; 'Nicholson, Karen' Subject: RE: [AccessD] MDW ByPass Surgery, Post Op When you first started working with this new MDW file you must have joined the workgroup using Wrkgadm.exe (in WINNT\SYSTEM32). All you need to do is rejoin the default workgroup by running Wrkgadm.exe and choosing the default MDW file in C:\WINNT\system32\system.mdw. Then Access won't ask for a password each time you run it. Using the shortcut that specifies the workgroup file avoids this problem completely. Lambert > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [SMTP:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, Karen > Sent: Thursday, November 04, 2004 12:05 PM > To: Access Developers discussion and problem solving > Subject: RE: [AccessD] MDW ByPass Surgery, Post Op > > That is what I was thinking - why put it on a user's machine? So that > makes sense. The backend is now in SQL and the security for the tables > is ruled by SQL. I can put something in the start up of the app to > identify the lan user id, and if they are not in my group of users, then > out they go. > > So... How does one get rid of the reference to the .mdw once one has > been established? If I open up any Access database, this stoopid thing > runs. On the web, it is telling me to re-install Access. Must be a > better way. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, > Lambert > Sent: Thursday, November 04, 2004 11:42 AM > To: 'Access Developers discussion and problem solving'; Nicholson, Karen > Subject: RE: [AccessD] MDW ByPass Surgery, Post Op > > > With no password, if you pass the user name in the command line then the > worst you'll have to do is hit enter when the password dialog appears. > Not > too arduous <g>. > > There is little point in having the MDW file on the user's machine. If > you > needed to move them into a different user group you would have to visit > the > workstation to do that. So the MDW should always be centrally stored, > available to all users. But note, the MDW is in fact just a plain > ordinary > MDB file with a different extension. As such it is subject to all the > usual > corruption risks, so I should be sure to backup the file at least once > every > day. > > If you do get a corruption of the MDW file, usually it is enough to open > it > with Access (from the File, Open menu) and run a Repair on it. > > Lambert > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [SMTP:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, > Karen > > Sent: Thursday, November 04, 2004 11:11 AM > > To: Access Developers discussion and problem solving > > Subject: [AccessD] MDW ByPass Surgery, Post Op > > > > What would you do if the PWD is null, none assigned in the .mdw? > AND... > > Is it OK to store the .mdw reference on a shared drive on the network > > instead of on an individual PCs folder? > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MG > > Sent: Thursday, November 04, 2004 7:27 AM > > To: 'Access Developers discussion and problem solving' > > Subject: RE: [AccessD] .MDW ByPass Surgery > > > > > > Try a shortcut on your desk, (watch for word wrap) viz: > > "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" > > "C:\_MCM\MCMFrontEnd.mdb" /wrkgrp "\\Server\svr-c\MCM\MySystem.mdw" > > /USER > > max/PWD max123456789 > > > > Regards > > Max > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, > > Karen > > Sent: 04 November 2004 12:13 > > To: accessd at databaseadvisors.com > > Subject: [AccessD] .MDW ByPass Surgery > > > > My database is hooked to a .mdw. During the development stage, I want > > to > > open up the database and bypass this nag screen that asks for the user > > name > > and password. I have been googling, but can't find too much. > > I would like the shortcut on my desktop to do it, I think. But at > this > > point I will do just about anything to disconnect it while I am > > developing. > > Thanks, wise ones. > > -- > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > --- > > Incoming mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.786 / Virus Database: 532 - Release Date: 29/10/2004 > > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.786 / Virus Database: 532 - Release Date: 29/10/2004 > > > > > > -- > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > -- > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com