TECH: Tips to avoid data loss with MICROSOFT PUBLISHER2006

Saturday, October 7, 2006

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.


JOBSEARCH: Rebuilt my Turkey Farm after SP koed it. http://tinyurl.com/lxu93

Saturday, October 7, 2006

http://tinyurl.com/lxu93

FWIW


TECH: MICROSOFT PUBLISHER2003 problem required rebuilding

Saturday, October 7, 2006

I had to rebuild the navigation bar from scratch. Arghhh! But, at least now it’s working. Argh! Arghhhh!

(Always doing over. Not creating new stuff!)


TECH: MICROSOFT PUBLISHER2003 bug?

Saturday, October 7, 2006

It is apparent after many struggles that the navigation bar index on a website is not recreated after one updates the website.

I found the following on MICROSOFT:

http://office.microsoft.com/en-us/assistance/HP062535831033.aspx

***Begin Quote***

* You may have a slow Internet connection, or you may be experiencing problems with your Internet connection. Check your connection speed or try to log on to your Internet Service Provider again.
* If your Web site loads slowly when you publish updates, check to see whether you selected the Enable incremental publish to the Web option. This option allows you to publish updates to a previously published Web site quickly by uploading only the files that contain the changes you have made.

ShowHow?
1. On the Tools menu, click Options, and then click the Web tab.
2. Under Saving, select Enable incremental publish to the Web.

HideAfter I published my Web site, some features did not work.

You may have published to a Web server (Web server: A computer that hosts Web pages and responds to requests from browsers. Also known as an HTTP server, a Web server stores files whose URLs begin with http://.) that does not have the most recent version of the FrontPage Server Extensions from Microsoft. Without these server extensions, certain features will not work, such as Web forms.

Contact your Internet Service Provider or network administrator to find out if the Web server or network server that you are publishing to has the necessary server extensions.

HideI published my updated Web site to the Web, but I don’t see the changes I made.

If you try to publish an updated version of your Web site to the Web, and your changes do not appear, it may be because you made previous changes to your Web site files directly on the Web server (Web server: A computer that hosts Web pages and responds to requests from browsers. Also known as an HTTP server, a Web server stores files whose URLs begin with http://.) or the network server. If you made changes to your Web site directly on the server, you will not be able to publish later updates to the site from the original .pub file by using the Publish to the Web command. This is because the files that you changed on the server will no longer match up with the files that Publisher exports.

To update your Web site by using the Publish to the Web command, you will need to ensure that Publisher publishes your entire Web site, and not just the updates to the .pub file.

HideHow?

1. On the Tools menu, click Options, and then click the Web tab.
2. Under Saving, clear the Enable incremental publish to the Web check box.

***End Quote***

This advice has no impact.

I’ll have to figure out how to force that update. Or each time one changes the site (no matter how small), it appears that it generates all new names for the subpages. That makes the pig point to the old page names in the navigation bar. This will make the product useless for it intended purpose. Or, one can go thru and manually rename the new files back to the navigation bar’s old names.

Arghhh!


TECH: Microsoft PUBLISHER2003 good idea but “holes”

Saturday, October 7, 2006

Using Microsoft Publisher2003 to build websites is “good”. I’ve been using it ever since I misplaced my copy of Front Office. Tonight, I had the interesting experience of rebuilding a site.

(Don’t ask. A previously built sight apparently “went bad” when the service provider mucked up some required files.)

SO, I rebuilt it. But not until I had to recreate 9 pages virtually from scratch. It was entertaining. (More entertaining than watching the Yankees choke.)

I have the site mostly all rebuilt, I shipped it up to the website. Filezilla objected that two of the site’s files were “in use”. So I exited out of publisher to free them up. All well and good.

I looked at the refurbished site and saw a couple of minor glitches. No big deal. Trivial to fix.

I fire up publisher and I can’t get the site back in publisher format. I can see each of the ten or so pages individually, but I can get the site-wide view needed to fix them.

Arghhh.

Now I have to either redo them again or figure it out.

At least I have a working site. Wonder if anyone will notice the mistakes.

I blame what happened on publisher.