MDB BUG #9006

[dbahooker]

I have a concern about the 'Log Messages' property of a Sql Passthrough
query; I would like to know why this doesn't work. From what I see,
this property doesn't do anything.

I am just concerned; because this is but one symptom that the Access
development team is being a bunch of slackers.

I call for Microsoft to spin off Access into a seperate company--
because Microsoft has demonstrated a thorough ineptitude with Microsoft
Access. The marketing problem with Access is even worse within
redmond; and I'm sick and tired of hitting a new bug every day.

i'm tired of all the workarounds, microsoft-- it is time to stop acting
like a bunch of 3-year olds.

Microsoft needs to spin-off Access, so that it can GROW into the
product that can effectively compete with Crystal Reports _AND_
coldFusion _AND_ Excel _AND_ Filemaker.

As it is; the bugginess of Microsoft Access demonstrates that Access is
doomed as a technology platform. As it is; anyone that uses Access in
the real world for anything should be shot-- Redmond has proven time
and time again that they dont know what the heck they are doing.

I just want MIcrosoft to quit the bullshit; and start taking Access
seriously. Instead of singing the praises of 'we tripled our access
team (oh yay, from 2 people to 6??)'

i just want to start seeing BUGS GETTING FIXED. I want to see BUGS
GETTING FIXED instead of people working on 'the latest, greatest, new
version'.

Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.
Quit the cycle, redmond-- start testing your products BEFORE you ship
them.


a) make a new SPT query. for example 'TRUNCATE TABLE MYTABLE'.
b) execute the query
c) see the notice 'Pass-through query with returnsRecords property set
to true did not return any records'
d) choose 'Log Messages = True'
e) execute the same query again- without changing the returnsRecords
property
f) notice the MSGBOX that says 'Pass-through query with returnsRecords
property set to true did not return any records'

g) DOESNT THE 'LOG MESSAGES' PROPERTY mean that
"messages returned from an SQL database are stored in a messages table
in the current Microsoft Access database."

on the other hand, the help file claims 'Error messages from SQL Server
aren't stored in the messages table.'

So wtf is this 'messages' talking about? We're talking about messages
that aren't error messages?

h) Why do i still get a MsgBox that says 'Pass-through query with
returnsRecords property set to true did not return any records' when i
set the 'log messages' = true?
i) more importantly, why doesn't the 'log messages = true' do as the
help file suggests; and record these messages into a table?

From the access help page

----------------------------------------------------------------------------------------
LogMessages Property
You can use the LogMessages property in an SQL pass-through query to
specify whether messages returned from an SQL database are stored in a
messages table in the current Microsoft Access database.

Note The LogMessages property applies only to pass-through queries.

Setting
The LogMessages property uses the following settings.

Setting Visual Basic Description
Yes True (-1) Microsoft Access stores messages returned from the SQL
database in a messages table.
No False (0) (Default) Microsoft Access doesn't store messages returned
from the SQL database.


You can set this property by using the query's property sheet or Visual
Basic.

Remarks
The name of the messages table where the returned messages are stored
is username - nn, where username is the logon name of the user running
the pass-through query, and nn is an integer that increases in
increments of 1, starting at 00. For example, if user JoanW sets the
LogMessages property to Yes and receives messages from an SQL database,
the messages table will be named JoanW - 00. If JoanW receives messages
in another Microsoft Access session (and the first table hasn't been
deleted), a new table named JoanW - 01 is created.

Note Error messages from SQL Server aren't stored in the messages
table.

 

[dbahooker]

oh wait a second.. Microsoft doesn't give a shit about access

i would reccomend than everyone in the world that uses access; move on
to a company that gives a shit
like oracle or mySql or IBM

Microsoft; i call for you to withdraw from the relational database
market altogether.

im sick and tired of wimpy managers buying Microsoft-- and me being
stuck with CRAPPY PRODUCTS