Problem with Opening/saving files in Dreamweaver MX

There is an issue with one of our workstations saving pages in Dreamweaver
MX. The trouble machine is a Mac running OS X. I am running Windows XP on
an IBM machine. When the Mac user opens a page and saves changes, I am no
longer able to open it. When I click on the page, I get an sharing
violation error, and then a message telling me Dreamweaver will shut down.
It then closes out the program. The server where the pages reside thinks
that the Mac user still has the page open. Today we had this happen again,
so we released the page on the server, and I went in and was able to
successfully open and save the problem page. The Mac user then went in, but
she is getting an invalid file marker error, and now she can't see the page.
This has happened on several different pages, in separate directories. I
have checked all her settings, and they all appear correct. We have a second
Mac user, but she is not experiencing any of these problems, so it appears
to be specific to this actual machine. Has anyone ever heard of something
like this happening?

is the "local site folder" for this site actually a network drive, that is
shared by all the machines?

IF you want to keep working like this (which i don't advise) check that the
drive is mounted or connected the same way on the two macs. There's
something different in their paths, or in the user's permissions on the
remote drive.

What should consider- is setting Dreamweaver up on each machine so that
each user has a site definition where the "local site folder" is Truly
local, inside of their machine. Then the "remote site" is the network share.
Enable file checkin/checkout to prevent overwrites.

then setup another site definition for publishing (only) to the final
production server- The network share is the "local" and the real server is
the remote.

There is an issue with one of our workstations saving pages in Dreamweaver
MX. The trouble machine is a Mac running OS X. I am running Windows XP on
an IBM machine. When the Mac user opens a page and saves changes, I am no
longer able to open it. When I click on the page, I get an sharing
violation error, and then a message telling me Dreamweaver will shut down.
It then closes out the program. The server where the pages reside thinks
that the Mac user still has the page open. Today we had this happen again,
so we released the page on the server, and I went in and was able to
successfully open and save the problem page. The Mac user then went in, but
she is getting an invalid file marker error, and now she can't see the page.
This has happened on several different pages, in separate directories. I
have checked all her settings, and they all appear correct. We have a second
Mac user, but she is not experiencing any of these problems, so it appears
to be specific to this actual machine. Has anyone ever heard of something
like this happening?

Thank you for your advice. I just want to make sure that I understand
exactly what we should do. Yes, the local site folder is a network drive
that we all have access to. The Mac users do not have permissions to work
on the live site, so we did not set up this share on their machines. If we
set up a 'local site folder' which is directly on their machines, we could
then make the "remote site' actually be the testing area they currently have
access to. Therefore, when they check a page out from the remote site, it
will overwrite what they have on their local drive, and when they check a
page in from their local drive it will move the page back to the remote
folder (which would actually be our staging area). Is this correct?

"Alan Ames _TMM_" <dont_mail_me (AT) formdude (DOT) com> wrote

is the "local site folder" for this site actually a network drive, that is
shared by all the machines?

IF you want to keep working like this (which i don't advise) check that
the
drive is mounted or connected the same way on the two macs. There's
something different in their paths, or in the user's permissions on the
remote drive.

What should consider- is setting Dreamweaver up on each machine so that
each user has a site definition where the "local site folder" is Truly
local, inside of their machine. Then the "remote site" is the network
share.
Enable file checkin/checkout to prevent overwrites.

then setup another site definition for publishing (only) to the final
production server- The network share is the "local" and the real server
is
the remote.

There is an issue with one of our workstations saving pages in
Dreamweaver
MX. The trouble machine is a Mac running OS X. I am running Windows XP
on
an IBM machine. When the Mac user opens a page and saves changes, I am
no
longer able to open it. When I click on the page, I get an sharing
violation error, and then a message telling me Dreamweaver will shut
down.
It then closes out the program. The server where the pages reside
thinks
that the Mac user still has the page open. Today we had this happen
again,
so we released the page on the server, and I went in and was able to
successfully open and save the problem page. The Mac user then went in,
but
she is getting an invalid file marker error, and now she can't see the
page.
This has happened on several different pages, in separate directories.
I
have checked all her settings, and they all appear correct. We have a
second
Mac user, but she is not experiencing any of these problems, so it
appears
to be specific to this actual machine. Has anyone ever heard of
something
like this happening?

Yes- exactly.

when there's more than one set of hands in a site, dreamweaver's
checkin/checkout will prevent other dreamweaver users from opening a file
that someone else is working on-

and yes, with checkin/checkout enabled, dw will use the newest version of a
file.

It's a safer workflow, and it will probably get rid of the file issues you
are having now.

so everybody has a site def that "publishes" to the network share Staging or
Testing server.

then some of you will have another site def, that moves the files from
Staging server to the Production server.

more info-
http://www.macromedia.com/support/dreamweaver/ts/documents/checkin_out.htm

Thank you for your advice. I just want to make sure that I understand
exactly what we should do. Yes, the local site folder is a network drive
that we all have access to. The Mac users do not have permissions to work
on the live site, so we did not set up this share on their machines. If we
set up a 'local site folder' which is directly on their machines, we could
then make the "remote site' actually be the testing area they currently have
access to. Therefore, when they check a page out from the remote site, it
will overwrite what they have on their local drive, and when they check a
page in from their local drive it will move the page back to the remote
folder (which would actually be our staging area). Is this correct?