DAO mdb to SQL Server Express?

I have a commercial product built with VB6 that has an mdb backend via DAO and I am happy with it.

There is a point with high usage among some clients where I will need to make an upgrade to something like SQL server Express in about a year's time.

MS are pushing this SQL server Express thing along with VB Express. I don't particularly want to get into the VB express thing but I wonder if any one here has ported DAO code to SQL server express.

Comments please...
.

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: Convert to ADO for SQL Server back end
    ... all of the work required to execute a query is done ... So, in your case, using ADO instead of DAO will achieve little or no ... > I did some preliminary work and upsized my Jet tables to SQL server. ... > faster accessing data from SQL server than it does from the Jet backend on ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Convert to ADO for SQL Server back end
    ... The rule more or less is, "for Jet objects, use DAO, for SQL Server ... >I've read through some posts on the ADO vs. DAO question. ...
    (microsoft.public.access.adp.sqlserver)
  • 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.conversion)