Actual command sent to access

[Ben de Vette]

Hi,

is it possible to see the actual SQL command which is sent to Acces when
using an OleDbDataAdapter?
Al I can see now is that an update command failed.
Why, is not told.

Thanks in advance,
Ben

[Carl Prothman [MVP]]

Ben de Vette wrote:

is it possible to see the actual SQL command which is sent to Acces
when using an OleDbDataAdapter?
Al I can see now is that an update command failed.
Why, is not told.

Ben,
Open the DataAdapter's UpdateCommand property, then drill down
on the SQL Update command that being used.

Note if you were using MSDE or SQL Server, you could use the
SQL Server Profile tool to see the actual command being sent.
But with Access, you are limited...

--

Thanks,
Carl Prothman
Microsoft ASP.NET MVP

[Ben de Vette]

Carl,

I already found this command string, but it is filled with the question mark
sign which still has to be filled with the parameters. I am looking for the
way to see the actual command sent.

Anyone?
Ben
"Carl Prothman [MVP]" <ca****@spamcop.net> wrote in message
news:ew**************@TK2MSFTNGP09.phx.gbl...

Ben de Vette wrote:

is it possible to see the actual SQL command which is sent to Acces
when using an OleDbDataAdapter?
Al I can see now is that an update command failed.
Why, is not told.

Ben,
Open the DataAdapter's UpdateCommand property, then drill down
on the SQL Update command that being used.

Note if you were using MSDE or SQL Server, you could use the
SQL Server Profile tool to see the actual command being sent.
But with Access, you are limited...

--

Thanks,
Carl Prothman
Microsoft ASP.NET MVP

[Ben de Vette]

Hi,

FOUND the problem.
I used a reserved word as a fieldname.

Why o Why is access itself not telling me NOT to use this name :-(

So, as always, the problem is easy, but hard to find.
For the people who want to know the reserved words:
http://support.microsoft.com/default...NoWebContent=1

Greetz,
Ben
"Ben de Vette" <Be****************@profiler.nl> wrote in message
news:10*************@corp.supernews.com...

Carl,

I already found this command string, but it is filled with the question mark sign which still has to be filled with the parameters. I am looking for the way to see the actual command sent.

Anyone?
Ben

Yep. Anytime you use (and i advise you do not) but any time you do you
usually have to encase it in Brackets. [Fieldname] Although if one can avoid
reserved words one should.

"Ben de Vette" <Be****************@profiler.nl> wrote in message
news:10*************@corp.supernews.com...

Hi,

FOUND the problem.
I used a reserved word as a fieldname.

Why o Why is access itself not telling me NOT to use this name :-(

So, as always, the problem is easy, but hard to find.
For the people who want to know the reserved words:
http://support.microsoft.com/default...NoWebContent=1

Greetz,
Ben
"Ben de Vette" <Be****************@profiler.nl> wrote in message
news:10*************@corp.supernews.com...

Carl,

I already found this command string, but it is filled with the question

mark

sign which still has to be filled with the parameters. I am looking for

the

way to see the actual command sent.

Anyone?
Ben