Lost MDW association, on MAC/VMware WindowsXP

[madEG]

Hello Gang,

I noticed that our organization's two mac's [that are running windows in a virtual/emulated environment] lost their associated security file - the mdw that is controlling these user's permissions - was set back to the default c:\...system.mdw instead of the one that was assigned by me when I rolled out the app.

I noted that microsoft came out with some updated last night... and wonder if anyone else noted something of the same?

I guess I'll can add the /wrkgrp path parameter in the app's shortcut... but still. It was odd that this happened just to the two macs, and not the 'normal' pcs...

Thoughts?

Thanks folks - have a great weekend!

-Matt G.

 

[Banana]

Are the files located within the virtual hard drives or somewhere else? How do they usually get the files? Furthermore, are the .mdw files stored adjacent to their corresponding database file?

 

[madEG]

>>Are the files located within the virtual hard drives or somewhere else?

The client side portion of the app is on the "c:\foldername\" on the harddrive of the mac. I imagine there is some area that is created when the virtual install is done that calls sme area on the mac's HD "windows writable only..." I guess... Honestly, I don't have a very strong handle on how VMware based machines work.

> How do they usually get the files?

Do you mean the MS updates? Unsure what you are asking...

>Furthermore, are the .mdw files stored adjacent to their corresponding database file?

Yes, they are. Further, the data/backend portion of the app is stored on a network drive that is mapped from the windows client app that is running on the mac.

So to recap - the client side portion is local to the mac's HD (whereever it stores the Windows info...) and the mdw and the backend mdb portion are on a mapped drive that points to a file server on the network.

 

[Banana]

I've observed some wonky behavior whenever we try to use files outside of virtual hard drives which usually went away if I move it inside. See if you can make a copy of .mdw and put it inside the virtual hard drive (e.g. local to the Windows client) and see if it goes away.

Furthermore, I believe you have to explicitly give permission to read and write outside of Windows environment, since Access requires you to have a full read/write permissions for the location you're working and it is possible that VMWare may be restricting that due to default setting. Look at the VM's Setting, in 'Sharing' and make sure the permission for the folder where the backend mdb results has Read/Write permission.

 

[madEG]

Thanks! Ok - After the publishing department -and their goofy max users go home for the night, I'll head down their and see what I can see.

Thanks for your insight Mr. Banana!