Troubleshooting code for export to text file.

I was wondering if someone would be willing to help me troubleshoot this code. I got the code from here: http://www.cpearson.com/excel/ImpText.aspx

I'm sure that it works fine. But I was trying to modify it to fit my needs. I can step through it fine, but it doesn't generate the text file for the cells I'm selecting. At least, I think I'm selecting them. I might have goofed up the cell ranges.

I want to select 15 rows in a single column. So each cell will go on it's own line in a text file, and I don't want any character separation. In the macro that calls the function(ExportToTextFile), I changed

Please Login or Register  to view this content.

to this

Please Login or Register  to view this content.

So here's the full code that I'm trying to debug. I have a separate macro that calls this function:

Please Login or Register  to view this content.

It appears that nothing happens when I get to this line of

Please Login or Register  to view this content.

If anyone can take the time to explain to me what I'm doing wrong, I would really appreciate it.

Thanks,
-gshock

If AppendData is false, you'll never open a file, yet the code continues. That's bad.

I can't envision why you would set the row and column numbers as you do. And if SelectionOnly is not true, you wouldn't set them at all.

Why do you have the OnError statement? The first step if you get errors is to find out why. Start by taking it out.

Take out Application.ScreenUpdating = False too, until the code is stable.

Edit: And in fairness to Chip, that code is modified substantially from the link. Did you try his code as-is?

Yeah, but you took out the wrong code. Go back to the original, pass the input parameters correctly, and step through it.

After you get it working, edit as desired.

Shg, thanks for your patience with me on this one.

Ok, I followed your suggestion and copied Chip's original code exactly. For my needs, I created a loop, and I'm calling the function 4 times for each iteration of the loop. I commented out the Application.Screenupdating=False, and the OnError statements as you suggested from your last post. When I step through the code, it seems to be grabbing the text that I want, but it's not creating the text file. Can you help me figure out what's wrong? Thanks again for your time. I'm very grateful for all of your help.

Please Login or Register  to view this content.

Regards,
-gshock

I just tried a small example and it worked find.

Do you rellay intend to open the file for Append (add your stuff to the end)?

These loop is unnecessary, arent't they?

Please Login or Register  to view this content.

Just

Please Login or Register  to view this content.

... but it's not creating the text file.

Sure you're looking in the right directory? The file is created immediately on execution of the Open statement.

That question is unrelated to this thread, so how about starting a new one?

BTW, as a general comment, when you get a versatile piece of code like that that does more than you need, hacking it to your lesser requirements is usually a bad idea. You may need more of the functionality on another occasion.

And as a courtesy, it's nice to put an acknowledgement of the author and a link to the source, especially if you share the code within your organization.

shg,

EDIT: Problem solved. With a little ingenuity, I managed to accomplish what I wanted. Thanks again.


DisregardNo problem. I'll be happy to post another thread. Sorry to get off topic.

I'm not sure I understand what you mean about hacking code for to lesser requirements. Which part are you referring to?

I've pasted a link to Chip's code in the comments of my macro. I just didn't include it in the code I've posted. Your point is well taken

Thanks for the help.

-gshock

I'm not sure I understand what you mean about hacking code for to lesser requirements.

I mean your original attempt to take out what you didn't need.

When an MVP posts code on their web site (versus a forum), it's usually pretty golden. If you modify it without knowing exactly what you're doing, you may mess it up. In the best case, it simply won't work (as here). In the worst case, you will introduce a subtle and occasional error that will have you pulling your hair out. Just use it and forget it until you reall need to change it.

That's all I meant. Glad we have you mostly sorted now.