Re: Is ODBC right for me?

* Definitely Linked Tables from what I have heard for some time now. When
Access 2000 & Access 2002 came out, Microsoft was pushing ADP but it is
definitely not the case with Access 2007. In fact, I think the new ACCDB
format utilises the new JET engine (and JET engine was supposed to be in
maintenance mode only!)

See http://www.tinyurl.com/y2yjzn

and have a look at the first paragraph of page 10 from the Microsoft
document above and I am sure you can infer what Microsoft impplies.

* I haven't done much testing with Access 2007 + new ACCDB format but AFAIK,
you need A2007 to use ACCDB. If you have a uniform enviroment where
everyone has A2007, ACCDB will probably be better (since the Microsoft
Access / JET engineers have exclusive control of the engine which enable
them to tune it to suit Access while the JET 4 engine is shared in the OS so
they can't change it easily). If you have a mixed environment, I think it
is safer to stick to the MDB / MDE format for the moment.

* I am confused about "VB" nowadays since it could mean either the old VB6
or VB.Net or VB2005 but don't you have to use some sort of interface such as
OLEDB to access data regardles of the BE engine? In my databases, I used
ODBC-linked Tables (for Forms , Reports, etc ...) but in code, I use mostly
ADO / OLEDB for SQL Server to access and manipulate data and the speed is
quite fast.

I think the major bottleneck in most database application is network
transmission bandwidth, not the database engine or the interface to the
database (I once added a million simple records one at a time to a JET Table
using DAO Recordset code and it took only about 3-4 seconds). I concentrate
on reducing the need to transfer data across the network to a minimum, e.g.
getting the SQL Server to do most processing and only pass back the
processed result to Access FE.

--
HTH
Van T. Dinh
MVP (Access)



"DIRN" <DIRN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:04CD459E-1686-41C1-90AF-A773661CF283@xxxxxxxxxxxxxxxx
Cindy & Van T.

Thanks for taking time to respond to my question. I still have three
lindering wunderabouts:

- Which approach (ADP vs. Linked Tables) to a Access FE / SQL Server BE
app
does MS consider best practice with the current revs of their Access & SQL
products?
- If, linked tables - how to choose between MDB and ACCDB?
- What did they really mean in the quote above about making an Access
FE as effiecient as a VB FE?

If you have any additional info or know of a resource who might be of
assistance please respond further.

Your help is so incredibly appreciated.

Best Regards,
David Hogan


.

Relevant Pages

  • Re: I dont know how to link VB to database (ODBC) table.
    ... The Provider/Driver -> Uses a Connection String to access a Database engine ... The Jet engine -> Uses your data store. ... Under TextBox Property ...
    (microsoft.public.vb.general.discussion)
  • Re: Is ODBC right for me?
    ... I think the new ACCDB ... format utilises the new JET engine (and JET engine was supposed to be in ... I think the major bottleneck in most database application is network ...
    (microsoft.public.sqlserver.odbc)
  • Re: Back-to-front introduction needed
    ... >working with a database engine of some kind. ... The engine does all of the physical IO in binary. ... The JET engine to provide the functionality to query and maintain ... But in the context of distributing a new program that can create and ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Sir Frank Whittle
    ... > last-ditch expedient by an air force facing imminent defeat; the Meteor ... Prototype Jumo 004A jet engine of the Me 262 used high nickel chrom ... Ministerium) or german air ministry technocrat Helmuth Schelp mapped ...
    (rec.aviation.military)
  • Scramjet To Be Tested
    ... DAYTON - The Pentagon has approved flight testing for a revolutionary jet engine ... five to eight unmanned X-51As at speeds up to seven times the speed of sound, ...
    (rec.aviation.military)