Error opening database with shortcut

[Guest]

I've converted about 15 Access 97 databases to Access 2003. The databases
are split with the FE on the workstation and BE on the server. The workgroup
file is also located on the server. I created shortcuts with the following
/wrkgrp command
lines:
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\Documents and
Settings\All Users\Databases\Database.mdb" /wrkgrp "\\Server\Data\Userdata\
Databases\Wrkgroup.mdw"

The problem is sometimes when I use the shortcuts, the databases open up
fine, and then 4 out of 5 times when I open the data databases, I get this
message.

Microsoft Office Access couldn't find file
\\Server\Data\Userdata\Databases\Wrkgroup.mdw. This file is required for
startup.

Any ideas why is opens sometimes and sometimes it won't?

 

[Joan Wild]

I would guess that you are losing your network connection intermittently.

 

[Guest]

I would guess that you are losing your network connection intermittently.

--
Joan Wild
Microsoft Access MVP



I didn't have any problem with Access 97. There must be some way that I can join a workgroup in Access 2003 without the risk of it switching back to the default system.mdw. I've already tried importing objects into a new database joined to my workgroup file and that does even work without the shortcut with the command line. If anyone has suggestions, please help. I have to secure these 15+ databases as soon as possible.

 

[Joan Wild]

You can use the workgroup administrator and make your secure mdw the default
one. However you'll then have to login for every database.



[/QUOTE]

 

[Guest]

You can use the workgroup administrator and make your secure mdw the default
one. However you'll then have to login for every database.




--
Joan Wild
Microsoft Access MVP



That's what I want to do, login to every database. I used the Workgroup Administrator to join the database to my workgroup file, but it will not stay. When I close out and reopen, the System.mdw is the workgroup file again. Then I join my wg file again and open the database and when I close and reopen, another workgroup file is created, System1.mdw. Everytime I join to my wg file, when I close and reopen, another wg file is created, ie. System2.mdw, System3.mdw, etc. I also opened a new db, joined my wg and imported the objects from the original db. The problem with this is everytime I open it, I have to join the workgroup and I have a lot of users that just are not capable of doing that and even for those that could, it would be a tremendous amount of added work, because some of them use 7 or 8 databases daily and they are opening and closing them off and on during the day. Is there any way to make my wg the default one without the risk of it changing as I mentioned

above.?

 

[Joan Wild]

You do not join a database to a workgroup file. The workgroup file is tied
to your Access session.

That doesn't make sense to me. I've never seen this. What is the name of
your secure workgroup file. Is it located in a folder that you have full
permission to?

Try creating a new workgroup file and put it in a different location. Use
dbEngine.SystemDB in the immediate window to determine the mdw file in use.

Then I join my wg file again and open
This usually happens if Access can't open the workgroup file specified as
the default (it's missing, or no permissions to the folder where it's
located).

 

[Guest]

You do not join a database to a workgroup file. The workgroup file is tied
to your Access session.

That doesn't make sense to me. I've never seen this. What is the name of
your secure workgroup file. Is it located in a folder that you have full
permission to?

Try creating a new workgroup file and put it in a different location. Use
dbEngine.SystemDB in the immediate window to determine the mdw file in use.

Then I join my wg file again and open

This usually happens if Access can't open the workgroup file specified as
the default (it's missing, or no permissions to the folder where it's
located).


--
Joan Wild
Microsoft Access MVP


I'm not quite understanding that Access can't open the workgroup file, because when I join my workgroup file, it gives a login and it works fine. Some of the users are using the databases and it is not changing my wg file. It's like sometimes it does and sometimes it doesn't. It's really frustrating and I'm about ready to go back to Access97.

 

[Joan Wild]

What you are describing doesn't make sense to me.

You join your secure workgroup file, thus making it the default to use for
every session of Access.

You open your database and you are prompted for a username/password.

Everything sounds fine.

'users are using the databases and it is not changing my wg file'

What does this mean? Why would you expect that users would affect your wg
file at all?

Do you mean that users are just able to open the mdb without logging in?
If so, then you haven't secured it properly. Their default wg file is set
to system.mdw that ships with Access. They shouldn't even be able to open
the secure mdb. If they can then you missed a step in securing it.

Just because you set your default wg to the secure wg, doesn't affect other
users. The default is only for that computer.

Get it secured properly first, and then make the secure mdw available to all
users (put it on the network). You can join each of their computer to this
secure mdw by default, however the recommended approach is to leave them
joined to system.mdw and instead provide a desktop shortcut to launch the
secure mdb. Its target would look like
"Path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure mdw"