Can't open exclusive through shortcut??!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Background:
2 machines, Machine A=XP, Machine B=W2K
Access XP on both
Secured DB set for default access = exclusive
dbw and mdb are in different directories, have slightly different names, so
not a typical locking problem

The problem:
on machine A, I can open DB either through Access file/open after changing
dbw appropriately or through shrotcut, get full permissions, full menus every
time.

On machine B, can open through Access file/open after changing to
appropriate dbw and get full permissions, full menus

HOWEVER, opening through shortcut on Machine B (with or without the /excl on
the command line) I get reduced menus and what appears to be shared access.
No toolbars, only File/Edit/Insert/Records/Window/Help on menubar.

So, what is wrong here? Any ideas? These are not replicas; database is not
replicated. (Database extension is modified from mdb to mdb2 to allow
synchronization between machines using the briefcase function without
replication since replication causes such a headache! Direct copies have
been tested as well with same problem.)

If you've got any suggestions... I'll take them!!! This one has been
killing me for several days!
 
Hi, Doug.

First, check your shortcut on Computer B. Make sure that it has the
explicit path and file name for the Access executable. If you do not use
the explicit path and file name within the shortcut, then the default
version of Access will be launched and the command-line switches will be
ignored, including the /excl.

The default path of the Access XP executable is:

"C:\Program Files\Microsoft Office\Office10"

If you find that the shortcut on Computer B isn't explicitly naming the path
and file name of the Access executable, then you should also check the
shortcut on Computer A for the same thing.

Also, in addition to Access XP, do you have some version of the Access
run-time installed on Computer B? I ask because that would explain the
minimal menus being used, even if a /runtime command-line switch was ignored
in the shortcut. In this case, the Access run-time version would be the
default version of Access being launched, instead of the retail version of
Access XP.

Perhaps someone else can give you advice on the Briefcase function, if
that's what's giving you problems. (I don't think this is the case,
though.) I don't use the Briefcase because I don't trust it.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Any human can read my reply E-mail address and should alter it so that a
message will be forwarded to me. Spammers who use my UNALTERED reply E-mail
address will only satisfy the SpamEater's hunger.)
 
Guuny -- YOU ROCK!! Thanks! That was exactly the problem. I didn't realize
that machine had a run-time executable, and the shortcut was explicitly
pointing to it. Cleared that up and all works well now. Thank YOU!!!
-Doug

'69 Camaro said:
Hi, Doug.

First, check your shortcut on Computer B. Make sure that it has the
explicit path and file name for the Access executable. If you do not use
the explicit path and file name within the shortcut, then the default
version of Access will be launched and the command-line switches will be
ignored, including the /excl.

The default path of the Access XP executable is:

"C:\Program Files\Microsoft Office\Office10"

If you find that the shortcut on Computer B isn't explicitly naming the path
and file name of the Access executable, then you should also check the
shortcut on Computer A for the same thing.

Also, in addition to Access XP, do you have some version of the Access
run-time installed on Computer B? I ask because that would explain the
minimal menus being used, even if a /runtime command-line switch was ignored
in the shortcut. In this case, the Access run-time version would be the
default version of Access being launched, instead of the retail version of
Access XP.

Perhaps someone else can give you advice on the Briefcase function, if
that's what's giving you problems. (I don't think this is the case,
though.) I don't use the Briefcase because I don't trust it.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Any human can read my reply E-mail address and should alter it so that a
message will be forwarded to me. Spammers who use my UNALTERED reply E-mail
address will only satisfy the SpamEater's hunger.)
Click to expand...
 
Glad it helped!

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Any human can read my reply E-mail address and should alter it so that a
message will be forwarded to me. Spammers are free to use my UNALTERED
reply E-mail address. I will *never* get those messages!)


Guuny -- YOU ROCK!! Thanks! That was exactly the problem. I didn't realize
that machine had a run-time executable, and the shortcut was explicitly
pointing to it. Cleared that up and all works well now. Thank YOU!!!
-Doug
Click to expand...
 
Back
Top