Me too, think it reads easier

Thanks!
So the only real big misstep of these past 40 or so years was saying "I do" rather than "let me think about it (??)"

@Alex or Gregory - Would you show an example of using Chr(34)?  I tried, and get an error. Below is the line I tried to change, but I get an error.

CurrentDb.Execute "INSERT INTO SeriesT (Series) VALUES (""" & NewData & """)"
CurrentDb.Execute "INSERT INTO SeriesT (Series) VALUES (" Chr(34) & NewData & Chr(34) ")"

Hi, ST. I think the problem is that, often, the Chr(34) must be concatenated. Thus:  & Chr(34) & NewData & Chr(34) & ")"
See if this does the trick. You can also use the single-quote (') instead of Chr(34) if this is less confusing.
It's odd, but I've been using "Chr(34)" since my "Paradox" days -- centuries ago! The form must have been Chr$34 or something, because I continue to 'say' "STRING" when I type the open paren (even though I don't type $). Old dogs.

Always break it up into steps, one by one, checking it still works at each stage.
Firstly do it with an actual value

INSERT INTO SeriesT (Series) VALUES ("A")

Then what is the thing you want to substitute?

Agreed. Well said, lad. Who would run through a mine field, but instead take slow, measured steps and smile after each proves a safe placement.

I personally don't use the double quote. Instead, use the ASCII character code for the double-quote (which is Chr(34)) to avoid confusion. Also, to avoid over crowding, I don't bother with naming the "table." stuff. The field name alone should suffice. Of course, this may mean no using the "utility" and working out the SQL to VBA string concatenation on your own. Ah, well. Had we some other pressing matter to attend? Italians say "Cheap is expensive, expensive is cheap." I find that what promises to be the short cut is often the long frustration that occurs just before you just do the thing the "long way."

You can use Chr(34) to avoid using double double-quotes.  For instance:

You can write:   s = Chr(34)
instead of:    s = """"

Or you can write:     sql = "SELECT * FROM Table1 WHERE field1=" & chr(34) & "value" & chr(34)
instead of:     sql = "SELECT * FROM Table1 WHERE field1=""value"""

But many would find the latter cases not that big of a deal.

I've decided that the double double quotes is less confusing! LOL

That's why I wrote the DDQ function. All you have to say is:

ID = DLookup("AuthorID","QuoteT","FullText=" & DDQ(TextLookupField))

or

CurrentDb.Execute "INSERT INTO SeriesT (Series) VALUES (" & DDQ(MyValue) & ")"

I don't use it myself because I've been writing these damn double-double quotes for 30 years, so it's second nature to me, but I find it helps new developers.

That's such an elegant solution. You're right, our attention gets hijacked by the prejudice of personal habit. Often (as a fault, I'm certain) code written with conventions every bit as good as -- but different than -- what I've been using for years tends to draw my focus to issues that don't really matter. It's like speaking with someone from a foreign country whose accent doesn't make their English any less comprehendible but seems almost like always having a tiny pebble in your shoe.

Thank you Richard!  I'm getting better at the double quotes, but do get stuck sometimes.  Thanks for the code.