Re: A bug in MS Access

Tech-Archive recommends: Fix windows errors by optimizing your registry

"=?Utf-8?B?cmFqZWV2MjAwNQ==?=" <rajeev2005@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in news:E5A4AF7B-9C4C-424D-A3E0-E31F6EAB98AF@xxxxxxxxxxxxx:

> You made confusion in me and i thought you were right. Now it seems
> as a
> bug in MS Access. And also a bug in ADO.Net because of the bug in MS
> Access.

THERE IS NO BUG -- all this is expected behaviour according to the way
that Access works; it's well documented in the Help, and in just about
every manual that has ever been written. It is behaviour turning up in a
slightly unusual and unexpected situation, but that does not alter the
fact that it's a _developer_ problem not a Microsoft one (and you don't
catch me saying that very often!).

Scenario one: a query like this

SELECT Something FROM Somewhere WHERE Location = [Enter
location here:]"

Bog-standard parameter query: if you are using VBA, then the DB Engine
will throw an error because the [Enter location here:] parameter was not
declared; while the Access GUI will intercept it and raise an input box.
This is normal expected behaviour and lots of people would be moaning if
it were any other way.

Scenario two: a query like this

SELECT Something FROM Somewhere WHERE [non existent field] = 10;

is actually exactly the same. Until Microsoft actually release their
Telepathy Extensions, Access has No Way Of Knowing that the [non existent
field] is not an undeclared parameter. So it reacts in the normal, time-
honoured, documented and expected way -- see above. No bug. No problem.

In this particular situation, it is the developer's responsibility to
ensure that he or she is releasing properly debugged code with (at the
very least!) no mis-spellings in the SQL. There is no excuse -- the
problem you are reporting here is one of lazy programming and inadequate
testing. Just this once, you cannot shift the blame onto Microsoft; you
have hour own house to get in order.

Hope that helps


Tim F


.

Relevant Pages

  • Re: A bug in MS Access
    ... In the delete query condtion, ... thought this is a bug and searched for the stage to report this.Atlast, ... >>> Microsoft as I was not knowing whom to report. ...
    (microsoft.public.access.modulesdaovba)
  • Re: ADP/2003 sends wrong query to SQL server
    ... then you can keep working while you wait for Microsoft to get back to you. ... Maybe SQL Server would work better for you. ... Access is issueing the wrong query, ... So there must be a bug in Access when putting a Pivotable in a subform.... ...
    (microsoft.public.access.adp.sqlserver)
  • Re: This is a Nice One (Bug)
    ... If you were charged for opening case SRX040813601170 about this bug, ... and I'll bring it up with Microsoft. ... Is that the hotfix that does not work in your case? ... It works for the sample query you provided, ...
    (microsoft.public.sqlserver.programming)
  • Re: IS NULL not working in WHERE clause.
    ... At this point it's pretty hard to say whether it's a bug or corruption. ... And just to be certain - you said the query operators each select ... in the query plan that checks time_id for null, ... >This execution plan shows a single execution string. ...
    (microsoft.public.sqlserver.programming)
  • Re: union all
    ... It certainly seems like a bug to me if 8 million rows vanish when you ... Provide the CREATE TABLE statements for CLAIMFL, CHKREG, CLIENT, ... script below (with your query inserted) in Query Analyzer and posting ... >union all ...
    (microsoft.public.sqlserver.programming)