No, I don't.
When used as special character (not just normal text in field as in O'Reilly or 1.0") they must be in pairs. And alternate their use. Use quote to define begin and end of a string. Then if you need to embed delimited parameters in that string, use apostrophes (or a doubled quote - which is called 'escaping' a special character - but I find that harder to read).
Text fields require apostrophe (or the doubled up quote) as delimiter for parameter.
Date fields require # character.
Number fields do not need delimiter.
Use of apostrophe and quote characters in data can cause issue with building SQL statements in code. So if a parameter needs to use 'O'Reilly' - the SQL will choke on that extra apostrophe. Use Replace function to double the apostrophe so it will be treated as a single normal text apostrophe, not a special character, if there is a chance data can have apostrophe.
Code:
CurrentDb.Execute "UPDATE tablename SET LastName='" & Replace(Me.tbxLName, "'", "''") & "' WHERE ID=" & Me.tbxID
Quote in data is even trickier. I have a database where I refuse to allow entries like found at depth 4.6" - not allowed to use quote character - spell out inches or convert to decimal feet. Somebody gets their hand slapped if they don't comply.