Can't find MDW file problem
- From: Salad <oil@xxxxxxxxxxx>
- Date: Wed, 15 Oct 2008 11:57:30 -0700
I have a situation where some, not all, users get the message "Couldn't find file "F:\AccessApps\AppName.mdw". This file is required for startup".
My app the users are attempting to access is written A2003 and they use the A2003 runtime to access the application. They use a desktop icon that specifies the location of Access, the Appname, and the MDW file to use. Ex:
"C:\ProgramFiles\Office\MSACCESS.EXE" "C:\Apps\App.MDB" /wrkgrp F:\Backend\App.MDW
The only users getting this message have A97 retail, A2000 retail, and A2003 runtime. All other users have A2003 runtime only on their PCs as well as Office 2007 products and they do not get this error message.
All users experiencing this problem have WinXP as their OS and all SPs are up to date. The office version they have is Office 2000 they use for other Office products like Word and Excel.
These users, if they want to use the program in A2003, must/always log into the same app in A97 first and then log into the app in A2003. In all desktop icons the MDW is specified.
At first I thought it might be a "rights" issue but I discarded that thought since they can log into the app with A2003 if they first open it (using the same MDW file) in A97.
This problem first cropped up using Tony Toew's AutoFE program. Since I don't have Tony's source code I couldn't determine if his program or my program was the source of the problem. I designed another method to distribute updates and the problem still occurs with my new method.
My temporary kludge fix is to have them run WrkGAdm.EXE and join to the MDW file on the network. This corrects the problem. This problem occurs only when I create a new update for them that requires distribution. After they have "rejoined" the MDW file after a new update they don't have the problem again until another update is created.
When I do an update, I create the updated version from a machine with a full version of A2003 attached to their network. I recompile the application and make an MDE from that machine. This machine is always attached to the MDW file on their network.
Does anyone have any idea why Access gives this message regarding the MDW file that is hard-coded/specified in the desktop icon? Why rejoining is the only solution at this point to solving the problem?
Could this be a registry problem? I am casting a jaundiced eye towards Office 2000 at this point as the culprit.
Any suggestions are welcome.
.
- Follow-Ups:
- Re: Can't find MDW file problem
- From: BruceB
- Re: Can't find MDW file problem
- Prev by Date: Access 2007: importing text date
- Next by Date: Re: Get list of the controls on a closed form
- Previous by thread: Access 2007: importing text date
- Next by thread: Re: Can't find MDW file problem
- Index(es):
Relevant Pages
|
