workgroup file on a thumbdrive?

[Rick B]

Hello:

I recently copied my personal files to a thumbdrive. When I try to create a
shortcut with the workgroup in it, I get the "you don't have the necessary
permissions..." error. If I use the workgroup administrator and join that
workgroup, then I am fine.

Did I build my shortcut wrong?

Target: "E:\Documents\Secured Accomplishment Tracking.mdb" /wrkgrp
"E:\RickSecure.mdw"
Start in: E:\Documents

Thanks!

 

[Joseph Meehan]

Hello:

I recently copied my personal files to a thumbdrive. When I try to
create a shortcut with the workgroup in it, I get the "you don't have
the necessary permissions..." error. If I use the workgroup
administrator and join that workgroup, then I am fine.

Did I build my shortcut wrong?

Target: "E:\Documents\Secured Accomplishment Tracking.mdb" /wrkgrp
"E:\RickSecure.mdw"
Start in: E:\Documents

Thanks!

I don't know thumb drives, but you need read, write create and delete
privileges on the drive where the database is stored. The message you are
getting indicates you don't have all those rights.

 

[Rick B]

Joseph, Thanks for the idea.

I can actually do it when I am joined to the workgroup (on the thumbdrive),
so I know I have all the permissions I need. I can see the locking file
created on that thumbdrive when I do open the file while joined to the
secured workgroup. I am able to do all my normal functions that way.

The only time I have the problem is if I join my default workgroup and try
to use the shortcut. I just assumed my shortcut might be wrong. Since the
preferred way to access a secured file is through a workgroup-specific
shortcut, I wanted to try to set it up.

 

[Albert D. Kallal]

When you use parameters in ms-access, you have to use the full path name to
msaccess.exe, and THE PARAMETERS set what file, and what workgroup file.

You don't mention what version of ms-access, but the shortcut for a2003 will
look like:

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE"
"C:\Program Files\Stampede\RidesXP.mde"
/wrkGroup "c:\Program Files\Rides.wrk"

Note that above would be all on one line (seperate each of the above by a
space).
Yours thus should look like

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE"
"E:\Documents\Secured Accomplishment Tracking.mdb"
/wrkgrp "E:\RickSecure.mdw"

So, the shortcut must point to msaccess.exe, and it is the parameters that
you change. the shortcut cannot point to the file...but only ms-access.exe
if you need parameters (if you don't need any parameters such as setting the
workgroup, then you *can* use a shortcut as you have)

 

[Joseph Meehan]

Joseph, Thanks for the idea.

I can actually do it when I am joined to the workgroup (on the
thumbdrive), so I know I have all the permissions I need. I can see
the locking file created on that thumbdrive when I do open the file
while joined to the secured workgroup. I am able to do all my normal
functions that way.
The only time I have the problem is if I join my default workgroup
and try to use the shortcut. I just assumed my shortcut might be
wrong. Since the preferred way to access a secured file is through a
workgroup-specific shortcut, I wanted to try to set it up.

If it is the workgroup issue, you can make a shortcut with the workgroup
specified.

From the help file:

Startup command-line options

The following table lists the Microsoft Access command-line options.

OptionEffect
database Opens the specified Microsoft Access database or Microsoft Access
project. Include a path if necessary. If you are running Microsoft Windows
95, the default path is your My Documents folder.
/exclOpens the specified Access database for exclusive access. To open the
database for shared access in a multiuser environment, omit this option.
Applies to Access databases only.
/roOpens the specified Access database or Access project for read-only
access.
/user user nameStarts Access by using the specified user name. Applies to
Access databases only.
/pwd passwordStarts Access by using the specified password. Applies to
Access databases only.
/profile user profileStarts Access by using the options in the specified
user profile instead of the standard Windows Registry settings created when
you installed Microsoft Access. This replaces the /ini option used in
versions of Microsoft Access prior to Access 97 to specify an initialization
file.
/compact target database or target Access projectCompacts and repairs the
Access database, or compacts the Access project that was specified before
the /compact option, and then closes Access. If you omit a target file name
following the /compact option, the file is compacted to the original name
and folder. To compact to a different name, specify a target file. If you
don't include a path in target database or target Access project, the target
file is created in your My Documents folder by default.

In an Access project, this option compacts the Access project (.adp) file
but not the Microsoft SQL Server database.
/repairRepairs the Access database that was specified before the /repair
option, and then closes Microsoft Access. In Microsoft Access 2000 or later,
compact and repair functionality is combined under /compact. The /repair
option is supported for backward compatibility.
/convert target databaseConverts a previous-version Access database or
Access project to the default file format, renames the new file, and then
closes Access. You must specify the source database before you use the
/convert option. To view the default file format, click Options on the Tools
menu, and then click the Advanced tab.
/x macroStarts Access and runs the specified macro. Another way to run a
macro when you open a database is to use an AutoExec macro.

/cmdSpecifies that what follows on the command line is the value that will
be returned by the Command function. This option must be the last option on
the command line. You can use a semicolon ( as an alternative to /cmd.
Use this option to specify a command-line argument that can be used in
Visual Basic code.
/nostartupStarts Access without displaying the task pane (the second dialog
box that you see when you start Access).
/wrkgrp workgroup
information fileStarts Access by using the specified workgroup information
file. Applies to Access databases only.

Notes
To run a Visual Basic for Applications procedure when you open a database,
use the RunCode action in the AutoExec macro or in the macro that you run by
using the command-line option /x. You can also run a Visual Basic procedure
when you open a database by creating a form with a Visual Basic procedure
defined for its OnOpen event. Designate this form as the startup form by
right-clicking the Database window, clicking Startup, and then entering that
form in the Display Form/Page box.
To specify a forward slash (/) or semicolon ( on the command line, type
the character twice. For example, to specify the password ;mjs/md on the
command line, type ;;mjs//md following the /pwd command-line option.

 

[Rick B]

lol. And back to my original post. I did create the shortcut. But, it
does not appear to work. When I use the shortcut, it still seems to use my
default workgroup. Instead of asking for my UserID and password, it issues
the error. Thus, my original question- is my shortcut correct? If so, what
could cause the default workgroup to be used when this shortcut is
double-clicked:

Target: "E:\Documents\Secured Accomplishment Tracking.mdb" /wrkgrp
"E:\RickSecure.mdw"
Start in: E:\Documents

 

[Rick B]

Albert:

Thanks!!! That did it. I had the file, the switch, and the workgroup, but
I did not include the application location as the first part of the
shortcut. Once I added that it worked!

Thanks!

 

[Rick B]

Joseph:

I got it. Albert's post reminded me that I had left out the application
path. Thanks for your help as well.

 

[Brendan Reynolds]

Hi Rick,

I don't have a secured MDB available with which to test this, so I could be
wrong, but I think you may need to specify the path to MSACCESS.EXE ...

"C:\Program Files\Microsoft Office\Office11\MSACCESS.EXE"
"E:\Documents\Secured Accomplishment Tracking.mdb" /wrkgrp
"E:\RickSecure.mdw"

 

[Rick B]

Brendan:

Thanks. The first line was the key. I did not include the actual
application path.

Thanks!

 

[Tony Toews]

I don't have a secured MDB available with which to test this, so I could be
wrong, but I think you may need to specify the path to MSACCESS.EXE ...

Correct. When passing any kind of a parameter to msaccess.exe you
must also specify the path and name of the executable. Note that this
is a Windows limitation and nothing to do with Access.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm