By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,175 Members | 1,710 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,175 IT Pros & Developers. It's quick & easy.

Can't find MDW file problem

P: n/a
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.


Oct 15 '08 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Oct 15, 1:57*pm, Salad <o...@vinegar.comwrote:
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.
Does it make any difference if you specify the \wrkgrp parameter
before the name of the .mdb file, i.e.

"C:\ProgramFiles\Office\MSACCESS.EXE" /wrkgrp "F:\Backend\App.MDW" "C:
\Apps\App.MDB"

Also, what do you have in the 'Start in:' field of the shortcut
properties?

Bruce
Oct 15 '08 #2

P: n/a
BruceB wrote:
On Oct 15, 1:57 pm, Salad <o...@vinegar.comwrote:
>>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.


Does it make any difference if you specify the \wrkgrp parameter
before the name of the .mdb file, i.e.

"C:\ProgramFiles\Office\MSACCESS.EXE" /wrkgrp "F:\Backend\App.MDW" "C:
\Apps\App.MDB"
I will have to check that one out. What would you recommend...the
folder that MS-Access.EXE is in or the folder where the MDB is in?
Also, what do you have in the 'Start in:' field of the shortcut
properties?
I really don't know. I'll check that out tho I don't know why it would
make a difference.
Bruce
Oct 15 '08 #3

P: n/a
On Oct 15, 5:22*pm, Salad <o...@vinegar.comwrote:
BruceB wrote:
On Oct 15, 1:57 pm, Salad <o...@vinegar.comwrote:
>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.
Does it make any difference if you specify the \wrkgrp parameter
before the name of the .mdb file, i.e.
"C:\ProgramFiles\Office\MSACCESS.EXE" /wrkgrp "F:\Backend\App.MDW" "C:
\Apps\App.MDB"

I will have to check that one out. *What would you recommend...the
folder that MS-Access.EXE is in or the folder where the MDB is in?
Also, what do you have in the 'Start in:' field of the shortcut
properties?

I really don't know. * I'll check that out tho I don't know why it would
make a difference.
Bruce
I would experiment with specifying the /wrkgrp parameter first, and
try different values for the 'start in' property of the shortcut,
i.e., try starting it in f:\backend, c:\program files\office, and c:
\apps, see if any of those correct the problem. It's a shot in the
dark, I admit.

Bruce
Oct 21 '08 #4

P: n/a
BruceB wrote:
On Oct 15, 5:22 pm, Salad <o...@vinegar.comwrote:
>>BruceB wrote:
>>>On Oct 15, 1:57 pm, Salad <o...@vinegar.comwrote:
>>>>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.
>>>Does it make any difference if you specify the \wrkgrp parameter
before the name of the .mdb file, i.e.
>>>"C:\ProgramFiles\Office\MSACCESS.EXE" /wrkgrp "F:\Backend\App.MDW" "C:
\Apps\App.MDB"

I will have to check that one out. What would you recommend...the
folder that MS-Access.EXE is in or the folder where the MDB is in?

>>>Also, what do you have in the 'Start in:' field of the shortcut
properties?

I really don't know. I'll check that out tho I don't know why it would
make a difference.

>>>Bruce


I would experiment with specifying the /wrkgrp parameter first, and
try different values for the 'start in' property of the shortcut,
i.e., try starting it in f:\backend, c:\program files\office, and c:
\apps, see if any of those correct the problem. It's a shot in the
dark, I admit.

Bruce
Thanks Bruce. I decided to remove the reference to the MDW entirely (it
doesn't seem to be used much in A2007. In my app the login was solely
used the login name for determining the currentuser and with A2003 I
updated to UserRoster to get the PC names of active users. I'll find
out tomorrow if it all works.

The error you are responding to is such an esoteric error although one
can see others have had the same problem if your search google.
Personally, I think it was the way O2K was installed...it may be they
used the same "root" folder that A97 was in when they installed A2K and
perhaps that confuses Access.
Oct 21 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.