I have developed a mental process to minimize the opportunity for losing data when using MICROSOFT PUBLISHER2006.
Assuming that one wants to have local copy and an inet copy of the website developed, I have four steps to avoid it.
(1) Create a directory where ever your local data store is. Make sure that this gets backed up and moved off site.
(2) Create a website somewhere on the inet.
MICROSOFT PUBLISHER2006 allows one to pubish and “pack2go”.
(A) Publishing creates the website.
(B) PACK2GO creates the input to PUBLISHER that can be edited.
SO I am doing !A, 1B, 2A, and 2B.
Belt and suspenders for me. Not having a method cost me rework time of the past uses.
Your comments and opinions would be welcome.
Reinke Faces Life 