[AccessD] DAO,VBA,A2K7? Update.

William Hindman wdhindman at dejpolsystems.com
Sat Jun 24 15:48:01 CDT 2006


...Here are some UNOFFICIAL answers that are from about as good a source as 
there is.
...inserted below with ####### identifier.

----- Original Message ----- 
From: "William Hindman" <wdhindman at dejpolsystems.com>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Sunday, June 18, 2006 11:13 AM
Subject: Re: [AccessD] DAO,VBA,A2K7?


> ...ok ...here's an abbreviated version of a list that Allen Brown 
> maintains
> plus some of my own gripes:
>
> Long standing bugs:
>
> 1) using Close method gives no warning if record cannot be saved 
> ...requires
> workaround to ensure data integrity.
>
> 2) Name Auto-Correct causes more problems than it addresses and is a
> performance hog ...at a MINIMUM the default should be off.
>
> 3) DAO not upgraded to reflect improvements in Jet engine and ADO 
> ...record
> level locking being an example ...I actually have to open a rs as ADO, set
> record level locking, and THEN change it to Dao in order to use this
> functionality native to Jet4.
>
> 4) the bookmark bug has resurfaced in every version in one form or 
> another;
> A2K3 required a hotfix to prevent writing the wrong record to SQL dbs.
>
> 5) data displayed incorrectly, i.e.: form detail section blank if no 
> records
> to display and no new records can be added ...which is bad enough but then
> controls in the form header or footer ARE visible but the data in them is
> wrong.
>
> 6) decimal fields sort incorrectly ...and when do we get a decimal data 
> type
> in VBA?
>
> 7) record level locking in Dao w/attached tables makes some transactions
> fail ...just love the consistency.
>
> 8) Allow Zero Length table property defaults to Yes ...are they begging 
> for
> trouble?
>
> 9) Subdatsheets default to Auto for Christ's sake!
>
> 10) Allow Design Changes defaults to True ...can they spell corruption!
>
> 11) select queries miss records i.e.: an outer join involving a literal
> value in the join field behaves as an inner join in Access ...that's just
> one example ...try querying linked SQL Server tables ...or not.
>
> 12) queries yield the wrong results when comparing anything to Null using
> the inequality operator.
>
> 13) the DISTINCT predicate is inconsistent in eval of nulls depending on 
> how
> the field is indexed.
>
> 14) DATES! ...how could they have not fixed the way access handles dates
> ...user types in a wrong format and Access GUESSES at what they meant
> ...often incorrectly ...and the numbnuts user is given no warning ...not 
> to
> mention the problems with how it handles international dates ...or 
> doesn't.
>
> 15) Currency format is not retained when Regional Options are changed 
> ...and
> works differently than the help file says.
>
> 16) no way to spec the data type for a calculated field which causes
> innumerable problems and workarounds.
>
> 17) RecordCount is deadly unless you use MoveFirst/MoveLast first. ...why 
> is
> this not native?
>
> 18) MoveNext without checking for EOF first can error ...why does this 
> still
> exist?
>
> 19) the HELP file ...the @#$%^&*(!@# NO HELP files!!! ...the design team 
> for
> the Access >97 help files should expect to spend a long, long time in
> purgatory ...does the Access development team realize just how many of us
> working in 2000, 2002, and 2003 feel compelled to retain and use the A97
> Help file because the subsequent ones were, imnsho, written by people who
> learned English as a Second Language and know zip about indexing? In point
> of fact, if word spread that the A2K7 Help file actually works, that alone
> would be sufficient motivation or me to upgrade.
>
> ...the REALLY aggravating thing is that all of the above are long-standing
> problems through several versions and require me to address them in every
> Access mdb I build ...and the A2K7 team wants to sell me a fancier gui and
> SharePoint integration instead ...like I said, they need a hard boot in 
> the
> crotch as a reality check.
>
> William
>
> ----- Original Message ----- 
> From: "Martin Reid" <mwp.reid at qub.ac.uk>
> To: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> Sent: Sunday, June 18, 2006 6:36 AM
> Subject: Re: [AccessD] DAO,VBA,A2K7?
>
>
> William
>
> I posted this questin to them a lot of weeks ago.
>
> Could you provide me with a list of the bugs that have been fixed in this
> release. Not new features BUGS FIXED.
>
> I am waiting for a reply.
>
> If you would like to frame up the question for me I will pass it on to 
> them.
>
> Martin
>
> Martin WP Reid
> Training and Assessment Unit
> Riddle Hall
> Belfast
>
> tel: 02890 974477
>
>
> ________________________________
>
> From: accessd-bounces at databaseadvisors.com on behalf of William Hindman
> Sent: Sat 17/06/2006 23:53
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] DAO,VBA,A2K7?
>
>
>
> ...did they get the single record locking in Dao recordsets fixed in 
> beta2?
>
> ...can't believe we get a new Access dedicated Jet engine and 99% of the
> changes go into the gui and hyping SharePoint services ...who the heck
> wanted SharePoint integration as their #1 priority? ...how about spending
> their time integrating ADO and DAO with the best features of each? ...if 
> the
> Windows types no longer control the Access engine, the Access team should
> stop trying to make it into a client/server fe ...that's VB.Net's niche
> ...or should be.
>
> ...at least it looks like the image bloating issue has been fixed at long
> last (what did it take, ten years?) ...but I'm not moving clients to A2K7
> just for that, a fancier gui, and SharePoint.
>
> ...someone needs to kick the MS Access team where it hurts ...if this is 
> all
> the meat in A2K7 I'm going to be putting a lot more time into SSE be's for
> A2K3 fe's for the foreseeable future and keeping an eye out for a viable
> Linux replacement down the road. :(
>
> William
>
> ----- Original Message -----
> From: "Martin Reid" <mwp.reid at qub.ac.uk>
> To: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> Sent: Saturday, June 17, 2006 3:31 PM
> Subject: Re: [AccessD] DAO,VBA,A2K7?
>
>
> At the moment William I would say no. DAO has some changes but mostly to 
> do
> with the new SharePoint related types, Attachment and Allow Multiple 
> Values.
>
> I am actually working with both DAO and ADO in 2007 and for all the day to
> day type stuff there would appear to be little changed at the moment.
>
> If you want to send me a sample I can test it out for you in terms of 
> speed
> etc in A2003 and A2007.
>
>
>
> Martin
>
> Martin WP Reid
> Training and Assessment Unit
> Riddle Hall
> Belfast
>
> tel: 02890 974477
>
>
> ________________________________
>
> From: accessd-bounces at databaseadvisors.com on behalf of William Hindman
> Sent: Sat 17/06/2006 20:23
> To: Access Developers discussion and problem solving
> Subject: [AccessD] DAO,VBA,A2K7?
>
>
>
> ...those of you working with A2007
>
> ...has there been any upgrade to DAO? ...the idea that in A2K3 I have to
> connect via ADO, set single record locking, and then change to DAO just to
> get that fundamental feature in DAO recordsets drives me nuts ...as does 
> the
> idea that ADO performance is so abysmal compared to DAO in local table
> lookups and many other areas as to be unacceptable ...has any of this
> changed with the new jetdb format in A2K7?
>
> ...any notable changes to VBA in A2K7 that would make the upgrade from 
> A2K3
> worth the cost and effort?
>
> William
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com 
> <http://www.databaseadvisors.com/>
> <http://www.databaseadvisors.com/>
>
>
>
>
>
> --------------------------------------------------------------------------------
>
>
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>> <http://www.databaseadvisors.com/>
>>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com 
> <http://www.databaseadvisors.com/>
>
>
>
>
>
> --------------------------------------------------------------------------------
>
>
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>>
>
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 






More information about the AccessD mailing list