I have access to a network drive which a I have set up to be available offline. Sychronisation occurs automatically when logging off. The problem I have is that when other users log onto to this machine, at logoff sychronisation is attempted for MY files, but fails because the netork drive is only available if logged in using my user name. Does anyone know how to avoid this. This could get very annoying if multiple users use offline files. Each user will have to see synchronisation fail for all other users.

Anonymous User 2/28/2005 9:03:21 AM

Nice article!

A problem for which I have yet to hear a (usable) solution:

(Assuming the process of enabling offline files on the server as well as locally, as described in your article, has been properly completed:)

Whenever something changes in a shared folder that has been made "available offline" (ie. copying, moving, creating, deleting or modifying a file or folder therein), not only the object(s) (files and/or folders) involved, but ALL folders along the path up to the "root" of the share as well, will automatically be tagged as "available offline".

While it might make good sense for MS to adopt this "better safe than sorry" behaviour, there are numerous good reasons for not wanting things to work this way (the prime being that it tends to cause a lot of added storage usage, disk fragmentation, synchronisation delays and network traffic). Unfortunatly, it appears that MS didn't make it possible to (easily, at least) change or modify this behaviour?

... But I'm hoping that someone might know a usable "workaround" or something..?


The behaviour I (and, I suspect, many others) need, would be something along these lines:

- Existing shared files and folders should not be made available offline "automatically", unless when the status is currently "working offline", in which case it is necessary in order to allow files to be added or modified in a folder that is offline.

- Files added to a shared folder should "inherit" the "available offline" status of the folder to which they are added, instead of always being set to "available offline" (ie. from the "immidiate" parent folder, as opposed to what I syspect is the current case, the "absolute" parent/shared/root folder.)


In case anyone know how this (or something similar) can be achieved, please contact me on the following e-mail address (remembering to de-obfuscate my anti-spam measures):

a:d;a:m;(amphersand):n;e:l;l:e;m:a;n:n;(dot):n;u


Regards,

Adam.

Anonymous User 1/24/2005 4:35:35 PM

As written in the text above:
Some file types—primarily database data files—don't work properly (or at all) offline. By default, Win2K disables Offline Files for files with a .db?, .ldb, .mdb, .mde, .mdw, .pst, or .slm file extension. When you configure a folder that contains these file types to be available for Offline Files, Windows displays (for each ineligible file) the error message Unable to make file filename available offline on \\\\servername\\sharename. Files of this type cannot be made available offline.

Mario 7/7/2004 7:07:25 AM

When i make offline file from mdb it show that Files of this type cannot be made available offline. Can anyone help?
Thanks

Aseel A 5/17/2004 5:33:25 AM