Generally when creating a Word file from either a Mac or Win7 pc and opening it on two different machines (either one first) it always prompts that the file is open and will be opened as read only. However opening a CSS file does not prompt that it is alr

Question

Generally when creating a Word file from either a Mac or Win7 pc and opening it on two different machines (either one first) it always prompts that the file is open and will be opened as read only.
However opening a CSS file does not prompt that it is already open on or from any machine which is causing code edits to be lost.
What we found from out testing:
- The file can be saved from one user to the server and WILL NOT PROMPT on other machines until the saving machine has the Dreamweaver program closed completely
- The file can be closed and  Dreamweaver minimised to the launch bar but it still will not register on other machines that it has been changed.
- Also, until the  Dreamweaver program is closed on the machines, it will continue to open it's saved version of the file. 
Example Scenario:
- User 1 opens test.css (which is 2000 lines) and adds some code to the end of the file to bring it up to 2500 lines
- Meanwhile User 2 opens test.css as well (opens as 2000 lines as User 1’s edits have not yet been saved) and adds in code to bring it to 2300 lines
- User 1 saves his file and closes it - but  Dreamweaver is still open.
- User 2 also saves his file and leaves  Dreamweaver  open.
- The server will report the size and last edit of the file the same as User 2 as he was the last person to save it (and if you open from the Win7 Machine it will show as User 2’s 2300 line version)
- If User 1 then open's the file again (from either the 'recent' in Dreamweaver OR clicking on the file directly in Finder...which version opens.... The version that User 1 saved! Not the true version on the server, but the version that User 1 edited and saved with 2500 lines in it.
- Same for User 2, he will open 'his' version with 2300 lines in.
Other information:
- Files are opened directly from the server
- Sometimes the users will save incrementally and re-open
- Most of the time users will save incrementally and keep the files open
- The users will never not save incrementally and just save when closing the file once finished
- The users are usually working on the files all day
- It is always the bottom lines of code that are lost. It could be a case of the two versions being mixed up and cutting off the newly added lines based on the line count (possibly).
It is as if Dreamweaver is holding a cache of the version locally and then only properly looking back to the server when it has been completely closed. It is very difficult to see how the server is causing such an impact on these files, there are very few logs which are giving any indication to the root cause of the problems.
Anyone know if this is a known issue?
Is there a way that there can be a featured implemented on the server that doesn't allow another user to open a file if it is already open on another machine?
Thanks

Answer 1

Your server file handling has nothing, and really nothing to do with Adobe software. If files don't get locked for (over-)writing and/or lose connection to the program opening them, then your server is misconfigured. It's as plain and simple and that. Anything from "known file types"/ file associations not being set correctly, MIME types being botched, crooked user privileges and file permissions, missing Mac server extensions, delayed file writing on the server, generic network timeout issues and what have you. Either way, you have written a longwinded post with no real value since you haven't bothered to provide any proper technical info, most notably about the alleged server. Either way, the only way you can "fix" it is by straightening out your server and network configuration, not some magic switch in Adobe's software.
Mylenium