SQLBill,
Thanks for your response. Allow me to provide you with some follow-up information.
By the way, the password to which I am referring is an application password which is one of ours, not SQL Server's.
I committed an error testing this in SQL Server because I was attempting to find a record that I had not yet saved with the changes. It couldn't find the record because it wasn't there yet! OOPS!
The explanation given (replacing each single quote with two single quotes)--resulting in 4 consecutive single quotes in this case--works in native SQL Server.
Unfortunately, it still doesn't seem to work coming through the provider from VB6. It seems to be a string manipulation problem in VB. I got around it once by substituting the
'''' with
''" & "'', but VB does some interesting things with strings manipulated like that. If I reference the string again (say to check for the occurence of another set of 2 single quotes, it converts it back to 4 consecutive single quotes (which doesn't work through the provider). I also ran into a strange thing (perhaps an "undocumented feature"

where using a
Replace(strSQL, "''''", "''"" & ""''"
command in VB makes the desired change, but also converts a single space to a double space. Go figure.
I am going to try a workaround. Maybe this issue should have been raised in the VB forum instead....
BlackburnKL