Has this been mentioned before? I get strange errors in Emplode when attempting to do searches for a backslash character.

Situation is... I'm trying to search through all of my song tags and locate instances where the file would produce illegal-file-name results when downloaded to the PC. For instance, if a song title contains a question mark ("Are You Okay?"), it would get converted to an underscore in the file name when downloaded to the PC ("Are You Okay_"). I'm trying to make sure my collection is edited to avoid that problem.

The illegal characters are:
\ / : * ? " < > |

In addition, I'm going to search for underscores, and certain patterns of hyphens and parentheses in certain fields which would screw up my ability to use my preferred filenames-to-tags pattern in Tag Studio.

By the way, how do I search for a double quote in a field using the emplode advanced search?

I would _guess_ that backslash is the escape character in Emplode ... try searching for \\ and quote as \". This is just a conjecture, mind you.

First thing I tried.

How 'bout:

title contains "\""

That's double-quote, backslash, double-quote, double quote.

Second thing I tried. Produces a different error message, but produces one nonetheless.

You sure? It worked for me...

You sure? It worked for me...

I get an error box saying Expected closing quote in 'title contains "\"'.

I get an error box saying Expected closing quote in 'title contains "\"'.

That's what I get when I do this:

title contains "\"

.
But when I do this:

title contains "\""

.
It finds songs with a double-quote in the title. The two outside double-quotes designate it as a string, and the backslash escapes the "middle double-quote"

Ah, OK, so that's how I find a quote. How do I find a backslash?

Um, get Roger to fix Emplode.

Unfortunately, Peter was smoking crack when he wrote the string tokeniser -- it can't cope with a backslash before the closing quote. I'll fix it later. In the meantime, search for:

title like "*\\*"

FITNR. Backslash inside a string literal now treats the next character literally. In other words...

"abc\"def\\gh\ijkl"

...is treated as the string literal...

abc"def\ghijkl

And there was much rejoicing.

Roger, YOU DA MAN.

And get Peter into a 12-step program.

A short term solution you can use my access application to import an emplode CSV dump of your database and search for slashes.

http://empeg.comms.net/php/showflat.php?Cat=&Board=empeg_general&Number=129202&page=0&view=collapsed&sb=5&o=0&fpart=2&vc=1

Ok... I have no business in this forum, much less this thread, but I always read through them anyway. I guess I do it hopes that I will some how gleen bits of knowledge from the masters. As I read this thread there was so much I didn't understand that my brain was desperately searching to find words it recognized. So much that I read this

In reply to:

---

Unfortunately, Peter was smoking crack when he wrote the string tokeniser

---

as Unfortunately, Peter was smoking crack when he wrote the string TOLKIENISER....cool so does it convert all the tags to tengwar.