Comments on: Running SQL from Visual Basic Code - Apostrophe problems! http://www.darraghmurray.com/access-tips-solutions/running-sql-from-visul-basic-code-apostrophe-problems/ It is not the critic who counts Fri, 21 Nov 2008 22:43:44 +0000 http://wordpress.org/?v=2.5.1 By: daz http://www.darraghmurray.com/access-tips-solutions/running-sql-from-visul-basic-code-apostrophe-problems/#comment-45 daz Tue, 18 Jul 2006 22:54:05 +0000 http://www.darraghmurray.com/general/running-sql-from-visul-basic-code-apostrophe-problems/#comment-45 As far as I know, that delimter doesn't work in Jet SQL. Access can take single ' ' delimters, but the way I propose is a functional way of doing it from code. Unfortunately, it seems that Jet inteprets the SQL different from VBA code than it does when using the normal query windows through its native interface. The reason why it is different, I shall have to find out! As far as I know, that delimter doesn’t work in Jet SQL.

Access can take single ‘ ‘ delimters, but the way I propose is a functional way of doing it from code. Unfortunately, it seems that Jet inteprets the SQL different from VBA code than it does when using the normal query windows through its native interface. The reason why it is different, I shall have to find out!

]]> By: David Young http://www.darraghmurray.com/access-tips-solutions/running-sql-from-visul-basic-code-apostrophe-problems/#comment-44 David Young Tue, 18 Jul 2006 06:10:44 +0000 http://www.darraghmurray.com/general/running-sql-from-visul-basic-code-apostrophe-problems/#comment-44 Does Access actually require postgres-style double-quotes around column names? SQL Server normally doesn't; but you could also try [] which is the other delimiter favoured by Microsoft DBs. Anyway, dealing with s*** like that is your deserved punishment for using VB (and not even VB.NET!) in the year 2006. Does Access actually require postgres-style double-quotes around column names? SQL Server normally doesn’t; but you could also try [] which is the other delimiter favoured by Microsoft DBs.

Anyway, dealing with s*** like that is your deserved punishment for using VB (and not even VB.NET!) in the year 2006.

]]>