"Sorry, can't find .mdw file."

[Marko Stojovic]

Following an earlier discussion, I've set up a database which has an AutoExec macro that prints out a report and shuts itself down again. I'm using NT4 (native) scheduler to do the task at a fixed time, and I've made a batch file that gives the instruction:

"c:\program files\microsoft office\office\msaccess.exe" "c:\winnt\profiles\ms67\desktop\schedu~1.mdb"

The weird thing is, when I click the .bat file it works fine, but when I schedule it, it says it cannot find the required workgroup file (it then gives the address of the .mdw file and says it doesn't exist, but it clearly does, and it's at the address specified! The MS-DOS name of the .mdw file is the same as the displayed name under the icon, so there's no confusion there).

Does anyone know why, when scheduled, Windows says it can't find the .mdw file which is exactly where it says it's not!?

Cheers,
Marko.

 

[kal-el]

I'm not sure why your having that problem but have you tried putting the workgroup file as part of the arguments to MSAccess
E.g.

"c:\program files\microsoft office\office\msaccess.exe" "c:\winnt\profiles\ms67\desktop\schedu~1.mdb" /wrkgrp "c:\winnt\system32\system.mdw"

 

[Marko Stojovic]

I just tried out your suggestion. The only difference is that my workgroup file address starts with \\... (a drive on the network), so it went something like "c:\program files\...msaccess.exe" /wrkgrp "\\pad-nt-...\mywrkgrp.mdw".

Unfortunately, I keep still getting the message "cannot find the required workgroup information file". The message mentions the address of the file, which is the same as the address I used, and I KNOW the file is there! Thanks for your suggestion, in any case.

Marko.

 

[Grandchester]

I use Access on a network drive, and it does not work when I specify the server name. It does work when I specify the letter assigned to that drive. Hope it works for you.

 

[Marko Stojovic]

Thanks. I'll give it a try!

 

[harrisw]

Just checking..

Is you workgroup file actually called "mywrkgrp.mdw".

If it is then thats your problem. I think access will always look for a "system.mdw"

Worth a try

 

[Marko Stojovic]

Yes, it's called mywrkgrp.mdw, but the thing is that the database opens OK when I run the batch file by double-clicking it (the file tells Windows to open Access.exe followed by the .mdb file). When I SCHEDULE it, that's when the problem occurs, but it's the very same batch file it's running in both cases!

 

[harrisw]

Try changing it to system.mdw and see if it makes a difference.

If not you can always rename it back

 

[mrfilez]

Disclaimer: I do not know much at all about Access. I am trying to learn it. The information below is based on what I have learned so far, and my knowledge of Win NT4. Please let me know if I am way off base with any of this.

You are using Win NT4. Do you have permissions to set something like that up in the security in Win NT4? Does the database have a login and password to it? That is usually when Access uses the .mdw file. You may have to setup something in the NT Scheduler for typing in the name and password if that is the case.

 

[harrisw]

You don't need to have local admin rights to change Access workgroup files.

 

[mrfilez]

I was not meaning to change the Access file. I was talking about changing what runs in the Scheduler. It depends on how permissions are set up. Where I work people do not have access to changing their printer. It is part of the security set up for each user.

 

[Marko Stojovic]

Thank you for your tips (I think this is probably currently the most discussed topic here!)

I don't actually have any security set up on the application at the moment, so I don't think that's the problem. I'll try changing the workgroup name to 'system', but I think it's all probably a glitch deep inside NT4. For instance, I can't click any icons to start my databases at the moment, but am forced to open access first and then choose a database/or run a batch file (without scheduling it). So, a bit of a mess.

I think I'll just have to accept it (a never-failing solution to everything!) - but thanks a lot for the suggestions.

Marko

 

[Pat Hartman]

Whatever you do, DON'T rename your workgroup to system.mdw. That is the default workgroup and your application will be totally unsecure on any computer but yours since their system.mdw's won't contain any security info.