FP03 publish to overwrite or not to overwrite

[Guest]

Have upgraded to FP03 from FP2k recently and have noticed what appears to be
a random pattern of behaviour in relation to overwriting files on the server.
On some occasions it asks if it should overwrite files on the destination
(as it should).

However, on some occasions it does not ask, and simply goes ahead and does
so. This is very dangerous since the files it overwrites are MDBs that store
user generated real time info (and so the local copy is almost surely out of
date), and thus destroys user supplied information. How can this be stopped?

Even more curious, and also in relation to MDB's, some times the local files
are more update than the server files, and they are different in every
respect (size, date, etc) and we with the publish process to update the
server files .. but it does not (it doesn't even ask). Again how can this
be? And why the random/inconsistent behaviour c.f. above.

 

[Kathleen Anderson [MVP - FrontPage]]

After an upgrade, it is recommended that you do a full publish from local to
remote, this will put both versions in sync. Afterwards, you can switch back
to changed pages only.

If you don't ever want the local database to be published to your remote
site, in FP 2003, you can right-click on the .mdb and mark it "do not
publish".

 

[Guest]

Thanks for that, and yes we know that and had done as much. Indeed, there
have been two independent full publications, and many changed pages only
pubs.

The issues is this, FP03 (unlike FP2K) is inconsistent in when/how it
decides to overwrite or not. We always want to be ASKED whether or not to
overwrite. IT SHOULD NEVER overwrite without our consent. Marking the db's
do not publish is something of a kludge since we do need to overwrite
sometime ... though at our discretion, not at FP03's discretion.

Would you have a solution for the "consistency" aspect of this enquiry?

 

[Guest]

An apparently related matter is that of borders. Again, for no apparent
reason, and without any consistency that we can determine, FP03 (though never
with FP2K) sometimes decides to change the theme in the left border, or to
overwrite bottom/top border during publish even though NONE of these had been
edited, altered, or touched in anyway whatsoever.

So what gives? How does it decide to completely alter look and feel? Why
is it uploading pages we have NOT changed (though clearly it thinks the pages
have changed, though why we cannot tell ...)

It’s a bit scary, and very dangerous.

Please advise