At some time, will you make the old page redirect to the new page
automatically?

At present, I'm just putting a note and link at the top of the superseded
pages pointing to the new page. Once I get the bulk of the pages converted
(it is a big job -- over 200 pages to convert) each html page will
automatically redirect to the corresponding aspx page. All aspx pages will
have the same name as the original html page, only with an 'aspx' extension
instead of an 'htm' extension. Due to the number of links pointing to my
pages as well as the Google Groups archives, the html pages will never go
away. Once an aspx page has been created, I will no longer update the html
page, but the html page will continue to be available.

I just changed web hosting services (more features, space, and bandwidth for
less money than the old provider) so I have space to keep two version of the
site running, the html version and the aspx version.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting
www.cpearson.com
(email on the web site)


"Dave Peterson" wrote in message
...
Chip,

At some time, will you make the old page redirect to the new page
automatically?

It'll make it slightly easier for google searchers and copy|paste posters
(like
me!).

Ps. I just read your "before you email me" page.
http://www.cpearson.com/excel/EmailMe.aspx

And thought that you may want to provide a note to try the newsgroups/MS
Communities or even search google before contacting you.



Chip Pearson wrote:

Yes, the example code on my web page was in error. I wrote the code years
ago and only very recently added the 4th parameter, which indicates
whether
to append the data to an existing output file (AppendData:=True) or to
purge
the output file before writing to it (AppendData:=False). I updated the
procedure code but neglected to update the examples. I have updated the
page
with the correct example code. I considered making it an Optional
parameter
but didn't because I felt that something as important as preserving or
killing off data shouldn't be left as a default behavior. For safety's
sake,
I wanted the user to have to explicitly state whether to kill off a data
file.

That said, I'm converting my entire site from simple and crude HTML to
fully
compliant XHTML 1.1 Strict with ASP.NET 2.0, and that particular page has
been superseded by the page www.cpearson.com/excel/imptext.aspx . The
aspx
page had the correct example code all along.

--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting
www.cpearson.com
(email on the web site)

"ryguy7272" wrote in message
...
This is probably something easy, but when you don?Tt know what to do
it is
hard. Basically, I copied Chip?Ts code form the following URL:

http://www.cpearson.com/excel/imptext.htm#Export

Then I run the code and the get an ?~Argument Not optional?T message.
The
following line is tinted blue:
ExportToTextFile

I looked at some DG topics that discussed ?~Argument Not optional?T
but didn?Tt
get anywhere. I Googled the topic, and tried to figure out what is
going
on...nothing jumped out at me. Basically, I didn?Tt find anything
that
seemed
helpful. I also looked under Tools References (I had my doubts about
this,
but tried it anyway). I clicked on Export 1.0 Type Library; it still
doesn?Tt
work.

Typically, I am resourceful, and try to resolve issues by myself, but
I?Tve
hit a wall, and don?Tt know what to do now. I thought I was just
starting
to
get somewhat proficient with this VBA stuff and then something that
should
be
extremely simple (can you say copy/paste) vexes me. Can anyone offer
some
insight or give me some kind of guidance

Thanks so much!

--
RyGuy

--

Dave Peterson