N prefix in SQL Queries for MFC DAO (using Visual Studio 2003)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi,

Just came across a peculiar problem, couldn't find anything on the web
documenting it. Am developing an ActiveX/COM dll which is to handle
data from an SQL Server 2000 DB; due to a new requirement, have to
handle an Arabic database as well, so I attempted adding the N prefix
on all strings in queries to indicate unicode (as I've done in queries
sent through C# as well as in Enterprise Manager), however DAO doesn't
seem to be recognizing it as valid syntax, I reckon its probably
outdated, and yes I really should be using ADO, but before I go
porting my code to ADO, was wondering if I'm correct in my assumption
that the cause is DAO. Anyone come across this situation before?

Thanks,
Nikhil

.



Relevant Pages

  • Re: Text of Startup Option Application Title
    ... This is a quote from Mary Chipman, SQL Server MVP, ex-Access MVP, and author ... DAO was designed, customized, and tweaked specifically for the Jet ... ADO was designed as a general-purpose data access wrapper around OLE ...
    (microsoft.public.access.formscoding)
  • Re: DAO vs ADO
    ... ADO ... > extra overhead retrieving metadata from the server for each query. ... > but I feel DAO is not as unsuitable as is often assumed. ... and ADO when working with SQL Server data. ...
    (microsoft.public.access.conversion)
  • Re: Connecting to a SQL Server 2005 using VBA and ADO
    ... dao should work just fine.... ... the above example when using sql server, or a plan Jane un-split database, ... I would not use findfirst even when not using sql server unless the data set ... Microsoft since they now seem to be favoring ADO. ...
    (microsoft.public.access.formscoding)
  • Re: DAO vs ADO
    ... The best rule of thumb to go by is: use DAO when working with local ... Access/Jet objects, and ADO when working with SQL Server data. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: DAO vs ADO
    ... The best rule of thumb to go by is: use DAO when working with local ... Access/Jet objects, and ADO when working with SQL Server data. ...
    (microsoft.public.access.conversion)