Access Inside Out

[Chris Hayes]

Hey. This is my opinion, but this ebook comes in handey. I really suggest
you get it if you are learning Access. The only draw back is his focus on
DAO. I would say ADO is the way to go nowadays but he's old school and I
can't blame him.

http://www.amazon.com/Microsoft-Off...9007839?ie=UTF8&s=books&qid=1179507476&sr=8-1

--
Chris Hayes
Still a beginner (only 12 years)

[fyi, you can email me by getting rid of the British Comedian''s name who
wrote that song about "Spam"]

 

[Arvin Meyer [MVP]]

The problem is that ADO is already been supplanted with ADO.NET and the 2
are far from similar. DAO is useful against all database systems which use
ANSI-92 SQL. ADO is slightly faster on some queries on a SQL-Server database
and is the only code supported in an Access ADP.

 

[dbahooker]

DAO is supported on an Access ADP, kid
don't spread mis-informatino

the FACT of the matter is that DAO doesn't 'look newer just because
ADO is obsolete'

DAO is a memory leak and anyone using it for anything should be fired
and then spit upon

The problem is that ADO is already been supplanted with ADO.NET and the 2
are far from similar. DAO is useful against all database systems which use
ANSI-92 SQL. ADO is slightly faster on some queries on a SQL-Server database
and is the only code supported in an Access ADP.
--
Arvin Meyer, MCP, MVPhttp://www.datastrat.comhttp://www.mvps.org/accesshttp://www.accessmvp.com

Hey. This is my opinion, but this ebook comes in handey. I really
suggest
you get it if you are learning Access. The only draw back is his focus on
DAO. I would say ADO is the way to go nowadays but he's old school and I
can't blame him.

[fyi, you can email me by getting rid of the British Comedian''s name who
wrote that song about "Spam"]- Hide quoted text -

- Show quoted text -

 

[Chris Hayes]

is it recommended that I focus on DAO also?

--
Chris Hayes
Still a beginner (only 12 years)

[fyi, you can email me by getting rid of the British Comedian''s name who
wrote that song about "Spam"]

The problem is that ADO is already been supplanted with ADO.NET and the 2
are far from similar. DAO is useful against all database systems which use
ANSI-92 SQL. ADO is slightly faster on some queries on a SQL-Server database
and is the only code supported in an Access ADP.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

Hey. This is my opinion, but this ebook comes in handey. I really
suggest
you get it if you are learning Access. The only draw back is his focus on
DAO. I would say ADO is the way to go nowadays but he's old school and I
can't blame him.

http://www.amazon.com/Microsoft-Off...9007839?ie=UTF8&s=books&qid=1179507476&sr=8-1

--
Chris Hayes
Still a beginner (only 12 years)

[fyi, you can email me by getting rid of the British Comedian''s name who
wrote that song about "Spam"]

 

[Chris Hayes]

I want to add and maybe clear a statement I made that didn't sound good. I
honor Mr Viescas and his knowledge. The man is a genious with access.
--
Chris Hayes
Still a beginner (only 12 years)

[fyi, you can email me by getting rid of the British Comedian''s name who
wrote that song about "Spam"]

 

[Larry Linson]

is it recommended that I focus on DAO also?

Jet is the default database installed with Access through Access 2003. DAO
is the native language of Jet. The Access team at Microsoft no longer
recommends ADO over DAO, as once was the case. The new, enhanced database
ACCDB of Access 2007 is directly descended from Jet, as are all its support
features/functions.

My experience with ADO has been limited to making modifications to an ADP
application with an SQL Server data store. I found that to be no "better"
than previous projects using DAO and ODBC to communicate with an SQL Server
data store.

If you're using ADO, if it does what you want, and if it doesn't take you
extra time and energy to use it, I wouldn't recommend you go change database
applications you have already written; on the other hand, I wouldn't
generally recommend starting a new database project using ADO to the
exclusion of DAO, either.

Larry Linson
Microsoft Access MVP

 

[Arvin Meyer [MVP]]

John Viescas is one of the original Access MVPs, and the only one still an
Access MVP. His skills, particularly with SQL are legendary. He is the "go
to" person that even we as MVPs use for the most difficult SQL questions.

Most, but not all, Access/Jet users, at least judging by the questions here,
prefer to use DAO.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

I want to add and maybe clear a statement I made that didn't sound good. I
honor Mr Viescas and his knowledge. The man is a genious with access.
--
Chris Hayes
Still a beginner (only 12 years)

[fyi, you can email me by getting rid of the British Comedian''s name who
wrote that song about "Spam"]

Hey. This is my opinion, but this ebook comes in handey. I really
suggest
you get it if you are learning Access. The only draw back is his focus
on
DAO. I would say ADO is the way to go nowadays but he's old school and I
can't blame him.

http://www.amazon.com/Microsoft-Off...9007839?ie=UTF8&s=books&qid=1179507476&sr=8-1

--
Chris Hayes
Still a beginner (only 12 years)

[fyi, you can email me by getting rid of the British Comedian''s name who
wrote that song about "Spam"]

 

[David W. Fenton]

Most, but not all, Access/Jet users, at least judging by the
questions here, prefer to use DAO.

And rightly so, as it makes more sense to use DAO for Jet data than
ADO, unless you need to do when of the handful of operations
supported by ADO that is not in DAO.

I do hope that MS rectifies that situation in the new DAO. Has
anybody checked in A2K7? Obviously, UserRoster isn't going to be
included, but maybe some of the field types that were left of DAO
3.6 are now included?

 

[dbahooker]

I'm not positive that I believe this:

The Access team at Microsoft no longer
recommends ADO over DAO, as once was the case.



Do you have that in writing?

I know that any Access person with any intellect says 'stfu and move
to VB.net'


Which uses ADO.. not DAO
Additionall, ADO is using in thnigs like Office Web Components which
have no replacement with DAO or ADO.net

I reccomend that you use one library for everything-- and one database
for everything
and that combination is SQL Server and ADO

 

[dbahooker]

I do anything I need via ADO

create a table?

THE CREATE TABLE TSQL
Why would I mix DAO and SQL in order to do something trivial like
that?


CREATE A QUERY? = CREATE VIEW TSQL OR CREATE PROCEDURE TSQL

Use of DAO is just flat out fucking stupid