By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,412 Members | 1,630 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,412 IT Pros & Developers. It's quick & easy.

DAO and SQL server

P: n/a
Sd
We are considering migrating a large piece of VB code from Access to
SQL server. All the code is in DAO, are there any known
incompatibilities WRT SQL server and DAO?

Many thanks
Si
Jul 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Sd (sd*********@hotmail.com) writes:
We are considering migrating a large piece of VB code from Access to
SQL server. All the code is in DAO, are there any known
incompatibilities WRT SQL server and DAO?


I have never used DAO, but a colleague of mine told me the other day,
that DAO was designed for Access, and is cumbersome to use with SQL Server.

In any case, DAO is old technology, and I would suspect that you don't get
full support for newer features in SQL Server with DAO, but I could be wrong
on that particular point. Nevertheless, I would consider ripping out DAO
in favour of ADO which is more up to date. Admittedly, I find ADO quite
ugly as well, and ADO .Net is a lot more palatable. That would however call
for a migration to VB .Net, which may be an overkill.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #2

P: n/a
"Sd" <sd*********@hotmail.com> wrote in message
news:e6**************************@posting.google.c om...
We are considering migrating a large piece of VB code from Access to
SQL server. All the code is in DAO, are there any known
incompatibilities WRT SQL server and DAO?

Many thanks
Si


There's stuff you can do with tables and queries which would probably cause
a problem.
You can forget compact and repair operations.
Table search is potentially a problem as you'll minimum have to switch to
(SQL) attached tables.
Hopefully the code and data is already split between two databases?

If you just use a bunch of selects and inserts then they're quite possibly
going to be relatively painless to convert.
If you have to do it anyhow.
I would suggest create corresponding sql tables manually.
Perhaps start off using DTS to load em in and see what you get.
Attach these to a copy of your code database.
Give it a twirl and see what happens.

--
Regards,
Andy O'Neill
Jul 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.