After reading help on the above topic I put the following lines into web.config: <system.diagnostics> <switches> <add name="SqlServerDQE" value="4" /> </switches> </system.diagnostics> just inside the configuration tag.

What I expected next was while running in debug mode after F5, all sql output would appear in output window, but nothing is appearing in ouput window.

Do I have to put trace commands around the getmulti statement? Or other?

Terry Voss

Hi Terry,

That's indeed should work without problems. Only to be sure, could you please provide your complete web.config code (without private information)?

Regards

Try the Immediate Window rather than Output?

I generally change the level on the fly around the query I want to see in more detail to avoid having to trawl through trace information I don't need:

' Store old level
dim OldLevel as integer = SD.LLBLGen.Pro.ORMSupportClasses.DynamicQueryEngineBase.Switch.Level

' Change level
SD.LLBLGen.Pro.ORMSupportClasses.DynamicQueryEngineBase.Switch.Level = TraceLevel.Verbose

' Run query
BookingListDynamic.GetMultiAsDataTable(fields, results, 0, sorter, filter, Nothing, True, Nothing, Nothing, 0, 0)

' Reset trace
SD.LLBLGen.Pro.ORMSupportClasses.DynamicQueryEngineBase.Switch.Level = OldLevel

Sorry for the dum question, but are you using a SQL Database for the SqlServerDQE?

Which runtime library version are you using?

It was all just looking in Output versus Immediate Window as it was all there in Immediate.

It would be nice if Help just showed the command example as that is what I really wanted which is to look at one complex getmulti:

Imports System.Diagnostics

SD.LLBLGen.Pro.ORMSupportClasses.DynamicQueryEngineBase.Switch.Level = TraceLevel.Verbose samps.GetMulti(bFilter, 0, bSort) SD.LLBLGen.Pro.ORMSupportClasses.DynamicQueryEngineBase.Switch.Level = TraceLevel.Off

This is going to allow me to use much more complex queries from code.

Thanks,