Prev: Localization in Crystal Reports
Next: Can be done?
From: Cor Ligthert[MVP] on 29 Mar 2010 07:50 Armin, I expected this answer, but I've read first what the OP sent. (I had almost connected my answer to your reply :-) ) > Sometimes I make mistakes and I would then like to check the text directly > on the sql server. Is it really to expect that this is needed for an Jet database engine? But nobody prevents you to get the Command.Text and replace the OleDB parameters which are then unnamed (and in fact ?) that yourself. I'm sure you know how to do that? :-) Cor "Armin Zingler" <az.nospam(a)freenet.de> wrote in message news:e9wH5LzzKHA.4328(a)TK2MSFTNGP04.phx.gbl... > Am 29.03.2010 09:46, schrieb Cor Ligthert[MVP]: >> Eric, >> >> Why inventing that wheel again with squares instead of a rounds. >> >> In my gives SQL profiler you back all the information you ask about? >> >> http://msdn.microsoft.com/en-us/library/ms187929.aspx > > How to determine the SQL I send to an Access database? > I send it but I don't know what I send. > > -- > Armin
From: Armin Zingler on 29 Mar 2010 10:37 Am 29.03.2010 13:50, schrieb Cor Ligthert[MVP]: > Armin, > > I expected this answer, but I've read first what the OP sent. I have no doubts. :) >> Sometimes I make mistakes and I would then like to check the text directly >> on the sql server. > > Is it really to expect that this is needed for an Jet database engine? Yes, I needed it. > But nobody prevents you to get the Command.Text and replace the OleDB > parameters which are then unnamed (and in fact ?) that yourself. > > I'm sure you know how to do that? > > :-) Even if I know how to do it, the String that I build is not the String that is sent to the database (engine). The latter is what I want to see. And if I already build the string myself, I could send it to the database instead of using the Parameters property, but isn't the latter recommended? -- Armin
From: Cor Ligthert[MVP] on 29 Mar 2010 12:23
Armin, I am not so sure that a complete string is sent, the command procedure is the same as with a stored procedure, where the mechanism of the parameters is used. http://msdn.microsoft.com/en-us/library/ms378675.aspx Cor "Armin Zingler" <az.nospam(a)freenet.de> wrote in message news:uJBQR20zKHA.4492(a)TK2MSFTNGP05.phx.gbl... > Am 29.03.2010 13:50, schrieb Cor Ligthert[MVP]: >> Armin, >> >> I expected this answer, but I've read first what the OP sent. > > I have no doubts. :) > >>> Sometimes I make mistakes and I would then like to check the text >>> directly >>> on the sql server. >> >> Is it really to expect that this is needed for an Jet database engine? > > Yes, I needed it. > >> But nobody prevents you to get the Command.Text and replace the OleDB >> parameters which are then unnamed (and in fact ?) that yourself. >> >> I'm sure you know how to do that? >> >> :-) > > Even if I know how to do it, the String that I build is not the String > that is sent to the database (engine). The latter is what I want to see. > And if I already build the string myself, I could send it to the database > instead of using the Parameters property, but isn't the latter > recommended? > > -- > Armin |