Access 2007 Workgroup

  • Thread starter Thread starter Chegu Tom
  • Start date Start date
C

Chegu Tom

I have a multi user access database with users that use access 2000, 2002,
2003 and now 2007

I compile (.mde) and distribute the front ends to each user. I compile with
2000 so it is compatible with all versions

I have a shared work group file that defines users and groups and which
access each has

Now I have a user upgraded to Access 2007, How do I get that user to join
the workgroup?

So for example I need to

open c:\program files\AccessMDE\production.mde
Using the shared workgroup S:\workgroup.mdw

Can I configure the access to use that workgroup (as in versions 2000-2003)
or do I need to use a command line option?

thanks

Tom
 
Realistically, for all versions of Access you should be using a shortcut
that includes the /wrkgrp flag. With Access 2007, I think that's the only
way.
 
Could I have some help with the syntax?

I have tried in a batch file just to open the databaser (not yet trying the
workgroup switch)

c:\program files\microsoft office\office12\msaccess.exe "c:\program
files\accessmde\production.mde"

I opens access fine but then give several not found errors ending with
cannot find "files.microsoft.mdb" which is not one of my databases. I
get the same error opening an mdb file.

Thanks
 
Chegu said:
Could I have some help with the syntax?

I have tried in a batch file just to open the databaser (not yet trying the
workgroup switch)

c:\program files\microsoft office\office12\msaccess.exe "c:\program
files\accessmde\production.mde"

You need a command with 4 elements in this pattern:

"Path2Msaccess.exe" "Path2Db" /WRKGRP "Path2Mdw"

You already had the first element (Path2Msaccess.exe), you just left out
the quotes which tell Windows to interpret it as all one thing.
(Without quotes, the spaces in the path cause Windows to think you're
asking it to evaluate 3 separate things rather than one.)

The same issue applies to Path2Db and Path2Mdw. If there are spaces in
the path, you need the quotes. It doesn't hurt to use the quotes
whether or not the path contains spaces.
 
Thanks


Hans Up said:
You need a command with 4 elements in this pattern:

"Path2Msaccess.exe" "Path2Db" /WRKGRP "Path2Mdw"

You already had the first element (Path2Msaccess.exe), you just left out
the quotes which tell Windows to interpret it as all one thing. (Without
quotes, the spaces in the path cause Windows to think you're asking it to
evaluate 3 separate things rather than one.)

The same issue applies to Path2Db and Path2Mdw. If there are spaces in
the path, you need the quotes. It doesn't hurt to use the quotes whether
or not the path contains spaces.
 
Back
Top