Text file/Excel problem. Any ideas?

[cordex]

That sounds like a lot of work, Cordex. I can combine my hand-written descriptions with what you've done. I can't ask you to do any more.

Meh. Maybe 30 minutes of coding (including the time it took to add a picture of my wife and daughter to the program's GUI at my daughter's behest).  Not that big of a deal at all.

Let me know whether or not it solves your problem.

[Monkeyleg]

Let me know whether or not it solves your problem.

I will, once I get the file to try out. Where is it?

[cordex]

I will, once I get the file to try out. Where is it?

I sent you a Dropbox email - did you not get it?  I can throw it on my website if you don't see it.

[Monkeyleg]

I got it. I finally gave up on trying to keep the long descriptions intact. Excel just won't do it. Some of the Leupold descriptions are 55,000+ characters.

I couldn't find another way to get text fields that big into Excel. If anyone knows...

[AZRedhawk44]

You won't be able to with Excel.

What is the DB engine on your website that will ultimately hold the contents?  MySQL?  Should have TEXT or MEDIUMTEXT datatypes available to store something that big.

Someone could directly import into your MySQL engine from the CSV rather than going through an Excel intermediary.

[cordex]

ML,
As I offered before, if you get me any other content you need joined to the descriptions (or just a list of SKUs you want exported, if that is all you need) and what you need the file to look like I will eat it ready without it ever seeing the inside of Excel.

At this point it really isn't much different than the other program I wrote - and in fact could be brought in to that pretty easily.

[GigaBuist]

Someone could directly import into your MySQL engine from the CSV rather than going through an Excel intermediary.

I've found that the MySQL text import tool actually works pretty good.  I use it for importing CSVs that I create from Excel documents to add new products and update inventory. 

Failing that a quick Perl script to rip CSV into SQL works too, as long as we're dealing with a small dataset (under 100k records) or you're not too concerned about runtime.

If the end target is MySQL feel free to kick it over to me via email, Monkeyleg.  I can figger something out. I do it probably 60-70 times a year.