Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Developer Toolkits / February 2007

Tip: Looking for answers? Try searching our database.

Ability To Point To Shared WIF

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
JJ of Eugene OR - 11 Feb 2007 18:16 GMT
Hello Group:

I am trying to use Access 2003 Developers Extensions.  I've often read that
one of Access's strengths is it's use for individual agency/workgroup uses.  
I have just such a workgroup application that I am trying to distribute using
the Package Wizard.  When the app gets installed on the user's PC, I need the
shortcut created by the Package Wizard to point to the existing shared
WIF/security file used by our agency.  

Most of our applications use SQL Server as the database and thus Access
security is not an issue.  Any old generic WIF will work in those cases since
I control security other ways.  For this application, however, there is a Jet
back-end database, and I need to control access/security through our agency
WIF.

The Package Wizard includes a screen labeled "Shortcut Properties".  This
screen allows me to specify a WIF/wrkgrp file.  However, entering a /wrkgrp
file in that screen results in the Package Wizard
copying of the shared agency WIF onto the user's hard-drive.  Entering the
WIF in the "Shortcut Properties" screen does not appear to result in a
shortcut that only points to the shared WIF on our LAN.  In the XP version of
the Package Wizard, we could specify custom shortcut properties, and thus
were able to point to a shared WIF.  But I don't see that option here.  What
am I missing?

Thanks,
- JJ, Eugene OR
Wei Lu [MSFT] - 12 Feb 2007 08:35 GMT
Hello JJ,

The file path you specified in the ShortCut properties is a parameter when
you open the database via the shortcut.

Per my test, when I use the shortcut to open the database, it will use the
shared WIF to get the security information.

But if I open the database directory, it will open the database without the
WIF.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
JJ of Eugene OR - 12 Feb 2007 16:19 GMT
Wei Lu:

Thank you for your help.  I appreciate the effort.

Unfortunately, I didn't understand what you wrote.  I don't know what you
mean when you say: "The file path you specified in the ShortCut properties is
a parameter when you open the database via the shortcut."

Let me try to explain again.  I'm familiar with a shortcut that uses this
format:
  "C:\PathToEngine\msaccess.exe" "C:\PathToMyApp\MyApp.mde" /wrkgrp
"X:\Path\WrkGrpFile.mdw"

I need the .mdw file at the end of the above example to point to our shared
.mdw file.  Here's what I have been able to figure out so far when I use the
Package Wizard:
   The Package Wizard has a screen labeled "Shortcut Properties".  In the
middle of that screen is a section with a label that says "Additional
Parameters".  (Is that the 'parameter' you are talking about?)  I go to that
section and check the box for "/wrkgrp".  Then I fill in the text box next to
that check box with the path to a .mdw file.  Here's what happens when the
Package Wizard is used:
a) Wizard creates a copy of the .mdw and puts it in the install package
b) When the package is run (ie, I run package to install the app on a
computer), the install package copies the .mdw to the application folder.  
For example, it creates a copy of the file in:
  C:\Program Files\MyAppFolder\MyWrkGrp.mdw
c) In the end, the install package creates a shortcut which points to the
above file--ie, the COPY of the .mdw file which is now in the application
folder on the local drive.

I actually want the above behavior for most of the install packages I
create.  And if I were distributing this app to another agency, the above
behavior would be necessary.  However, in this case (for an app that must use
a .mdw file for the database), here is what I need to happen instead:
a) No copies are made of the shared .mdw file at all
b) When package is installed, the shortcut points to the shared .mdw file on
our network/LAN (The shortcut does *not* point to a copy of the shared .mdw
which got copied onto the user's local hard drive).

Does that make sense?  Can you explain your answer in light of where I am
coming from?  I know I'm missing something.  I just don't understand what it
is.

Thanks!
- JJ, Eugene OR
Wei Lu [MSFT] - 13 Feb 2007 06:51 GMT
Hello JJ,

Thank you for update.

I did reproduce this issue on my side.

This is a by design issue.

I would like to check with internal team.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.