[AccessD] workgroup file (Sec Poll spin-off)

Erwin Craps Erwin.Craps at ithelps.be
Thu Nov 13 10:03:35 CST 2003


Roaming profiles sometimes do weird stuff...
Even when access is in same location.
I seen paths like "C:\Program Files\Microsoft
Office\Office10\MSACCESS.EXE" changing to
C:\Progra~1\Micros~2\Office10\MSACCESS.EXE in a sole Windows 2000 and XP
environment.

So I tend to believe there is still some code in windows that uses 8.3
naming conventions ... And this can create problems...
Because mircos~1 is not necesarily the short for Microsoft Office!! In
this case it was short for Microsoft Intellipoint because I installed
the mouse driver before Office.

Same thing with the default workgroup file its always system.mdw (the
localdisk one) and when using profiles in this or that situation it
sometimes changes to system1.mdw and creates it without asking.

But indeed /wrkgrp should solve this.



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Thursday, November 13, 2003 4:01 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] workgroup file (Sec Poll spin-off)


Hi Erwin

> I believe I'm not with with you....

> First, to set thing strait. It's only in our office for develepmont 
> I'm speaking.

Yes.

> Second.
> You mean you have a shorcut that starts msaccess.exe with /workgroup 
> xxx?

Yes. As I have one for starting a decompile.

> Problem with that is that you need a hard path to msaccess.exe and 
> hard paths is something I try to avoid.

No big problem here. All Access versions have remained where they were
installed - four of them for 38 months. I see no reason to move them
around.

> I always use roaming profiles and hard paths can problematic. I supose

> solutions are out there, but I already played alot with them and they 
> are often OS dependent.

That's a difference. I live in a Novell environment.

> You know, Gustav, It's not that a big deal...
> It's rarely I do a repair...

I know. But you mentioned it as it could cause problems to run an Office
repair and it really shouldn't be (regarding this topic).

> And I don't use workgroups anymore at customer sites.
> I use the network user name and match them with the users in the 
> database (user management based on tables/forms). If a network user is

> unkown in the database it exits instantly (after a msgbox).

I like that approach too. Also - as few clients have Single-Sign-On
implemented - it's a good service to the user that the app knows who
he/she is and all that is needed is nothing (in your case) or the
password only (in our case).

/gustav


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav 
> Brock
> Sent: Thursday, November 13, 2003 3:21 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] POLL: Access Security


> Hi Erwin

> In my opinion it is not a good idea to have a special mdw assigned as 
> the default. I have a shortcut for such an Access with the wkrgrp 
> switch opening a secured database.

> /gustav


>> I know...I know...
>> At least I supose you mean that you can give msaccess.exe an /wrkgrp
>> command line option. Or use the /profile and a profile file.

>> I only use MDW for developing purposes indside the office and just
>> want it always to be my company.mdw group...

>> Specifying company.mdw for default gets reset to system.mdw in the
>> user profile folder.... Or is it in the program Files/common
folder...

>> ?

>> Don't bother, I just overcopy all system.mdw with company.mdw...


>> Erwin

>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav
>> Brock
>> Sent: Thursday, November 13, 2003 1:56 PM
>> To: Access Developers discussion and problem solving
>> Subject: Re: [AccessD] POLL: Access Security


>> Hi Erwin

>> You can supply your app with your own mdw, say erwin.mdw. Office
won't

>> overwrite that. For that kind of apps we create shortcuts (menu 
>> entries) which makes it easy for the user to open the app with the 
>> needed command line.

>> /gustav

>>> .. I want to add that a office repair each time reset or overwrites
>>> your MDW file).

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


More information about the AccessD mailing list