Mapping Report Model Entities to Drill-through Reports

When you use Sql Mgmt Studio to assign a report as a drill-through target for
a model entity, you can assign reports for both "Single Instance" and
"Multiple Instance". Does anyone know what this means? I had a 2+-hour
support session with a member of MS SQL Reporting team, and he didn't know
either.
cheers,
Helen
--
Helen Warn, PhD
Agile Software Inc.
www.agile-soft.comBy default when you save the file, where the datasource is connected through
RB,
If you have opened RB through some other server then you can attach where it
is for multiple instance of the servers. Basically to update on the report
server database of multiple servers is called multiple instance and single
server is called single instance.
Amarnath
"Helen Warn" wrote:
> When you use Sql Mgmt Studio to assign a report as a drill-through target for
> a model entity, you can assign reports for both "Single Instance" and
> "Multiple Instance". Does anyone know what this means? I had a 2+-hour
> support session with a member of MS SQL Reporting team, and he didn't know
> either.
> cheers,
> Helen
> --
> Helen Warn, PhD
> Agile Software Inc.
> www.agile-soft.com|||Actually that is not what it is used for. From
http://msdn2.microsoft.com/en-us/library/ms345298.aspx
(Lesson 12: Specifying Clickthrough Report Options from BOL):
"There are two clickthrough templates for each entity: a single instance
template and a multi-instance template. A single instance template is used
when the user clicks an instance of the entity. A multi-instance template is
used when the user clicks an aggregate value and multiple instances of the
entity are displayed."
I am sure that I am not the only person who fervently wishes that the
reference sectins of the documentation contained such information.
Cheers,
Helen
--
Helen Warn, PhD
Agile Software Inc.
www.agile-soft.com
"Amarnath" wrote:
> By default when you save the file, where the datasource is connected through
> RB,
> If you have opened RB through some other server then you can attach where it
> is for multiple instance of the servers. Basically to update on the report
> server database of multiple servers is called multiple instance and single
> server is called single instance.
> Amarnath
> "Helen Warn" wrote:
> > When you use Sql Mgmt Studio to assign a report as a drill-through target for
> > a model entity, you can assign reports for both "Single Instance" and
> > "Multiple Instance". Does anyone know what this means? I had a 2+-hour
> > support session with a member of MS SQL Reporting team, and he didn't know
> > either.
> >
> > cheers,
> >
> > Helen
> > --
> > Helen Warn, PhD
> > Agile Software Inc.
> > www.agile-soft.com

Many left joins and slow performance

I am combining several columns and tables and I am wondering if there is a way to improve performance, for instance can I write an implicit join version of the following code, rather than having these explicit joins?

objCmd = new OleDbCommand ("SELECT MAmunicipalities.*, MAcitytown.*, countiesalias1.countyname, countiesalias1.countylinktitle AS clink1, countiesalias2.countyname, countiesalias2.countylinktitle AS clink2, countiesalias3.countyname, countiesalias3.countylinktitle AS clink3 FROM (MAmunicipalities LEFT OUTER JOIN MAcitytown ON MAmunicipalities.citytown = MAcitytown.citytown) LEFT OUTER JOIN MAcounties AS countiesalias1 ON MAcitytown.county1 = countiesalias1.countyname LEFT OUTER JOIN MAcounties AS countiesalias2 ON MAcitytown.county2 = countiesalias2.countyname LEFT OUTER JOIN MAcounties AS countiesalias3 ON MAcitytown.county3 = countiesalias3.countyname WHERE MAmunicipalities.municipality='plymouth'", objConn);

Sadly, I have even more joins left to add as well as other columns to add to the SELECT statement and more aliases to add as well. Any thoughts would be greatly appreciated.

So far, this appears to be a five table JOIN. That in itself 'shouldn't be a preformance issue.

Judicious usage of TABLE aliases would make the code a bit more readible (and maintainable).

And it is widely considered a 'best practice' to specifically identify columns instead of using [ SELECT * ].

For Example:

Code Snippet

SELECT
m.*,
c.*,
c1.CountyName,
c1.CountyLinkTitle AS cLink1,
c2.CountyName,
c2.CountyLinkTitle AS cLink2,
c3.CountyName,
c3.CountyLinkTitle AS cLink3
FROM MaMunicipalities m
LEFT JOIN MaCityTown c
ON m.CityTown = c.CityTown
LEFT JOIN MaCounties c1
ON c.County1 = c1.CountyName
LEFT JOIN MaCounties c2
ON c.County2 = c2.CountyName
LEFT JOIN MaCounties c3
ON c.County3 = c3.CountyName
WHERE m.Municipality = 'plymouth'

Are there additional tables to JOIN, or is it additional JOINs to the same tables (like with MaCounties above)?

|||I have additional tables to join. Right now it is taking between 10 and 15 seconds for a page to load using the code that is posted. I have indexed columns within those tables which has helped somewhat but it is still taking way too long. I suspect that having varchars being joined instead of ints is also contributing to the problem. Would a stored procedure help?|||

A stored procedure may help some -but its doubtful that it would provide the kind of improvement you really need.

As you suspect, the major issue is most likely the varchar() fields used for the JOINs.

One of the most significant things that help with speed on JOINs is the 'width' of an index. An integer field is 4 bytes. A varchar() field is as many bytes as characters (nvarchar() is double that.) The 'wider' the index, the fewer entries on an index page, therefore the more pages that have to be 'crawled' through and read to find the data.

Ideally, your CityTown and CountyName values would be integer values (CityTownID and CountyNameID).

I suggest that you explore using the Database Tuning Advisor to get assistance in fine tuning the indexes.

Refer to Books Online, Topic: 'Database Engine Tuning Advisor'

manual way to rename instance of analysis server?

is there a way to manually rename my instance of analysis server 2005? i have a 32bit machine, and the 32bit version of sql server 2005 and analysis server 2005 installed, yet i continually get an error. this happens on my servers too, which are all 32 bit. does anyone know of a manual work around ( via regestry maby) to rename an instance?

You should not need to rename an instance.

Can you tell us what error you are getting? There may be another solution to your problem.

|||Yes, there is a way to rename the instance. Search for ASInstanceRename.exe program under %Program Files%\Microsoft SQL Server. But, as Darren has suggested, you might want to not do it right away because it might not fix your problem and make things even worse since it is unknown what is causing your current problem. The utility operates on registry, service control manager, some setup related stuff, performance counters, redirector etc.

Managing 2000 and 2005

Dear all
I have now a default instance of SQL Server 2005 running on one PC and an
old default instance of SQL Server 2000 running on another PC.
I would like to administer both SQL Servers with the new SQL Server 2005
Management Studio. However, I am unable to register the SQL Server 2000 in
the SQL Server 2005 Management Studio.
Any help is appreciated.
Best regards
Adrian
Firewalls?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Deal all
Thank you very much for the excellent and very quick help.
Yes, the connection is established.
The trick is:
i) to follow this advice:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
but
ii) not to follow this one:
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
Now my sleep will be peaceful.
Best regards
Adrian
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||You should be able to.
What problems are you seeing?
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>
|||Adrian wrote:
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>
"Unable to register" means what exactly? Are you getting an error
message? Management Studio is perfectly capable of working with a 2000
server, I do it all day long every day...
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525017F.8020007@.realsqlguy.com...
> Adrian wrote:
> "Unable to register" means what exactly? Are you getting an error
> message? Management Studio is perfectly capable of working with a 2000
> server, I do it all day long every day...
Well, it is great to hear it. So I just need to figure out how.
I can connect to the SQL Server 2000 with the sqlcmd program within an eye's
blink. However, when I enter precisely the same connect data to the
register-dialog of the Management Studio it returns after quite a long time
a message with the error 10061.
So what am I doing wrong?
Adrian

>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||You should be able to connect to a SQL Server 2000 box from the SQL Server
2005 tools (including SSMS, Profiler, and the Replication Monitor
(sqlmonitor).
Keith Kratochvil
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>
|||Adrian wrote:
> Well, it is great to hear it. So I just need to figure out how.
> I can connect to the SQL Server 2000 with the sqlcmd program within an eye's
> blink. However, when I enter precisely the same connect data to the
> register-dialog of the Management Studio it returns after quite a long time
> a message with the error 10061.
> So what am I doing wrong?
That error indicates that the connection was refused by the server. Is
SQL Server using TCP/IP? Listening on what port?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45250DE5.8030609@.realsqlguy.com...
> Adrian wrote:
> That error indicates that the connection was refused by the server. Is
> SQL Server using TCP/IP? Listening on what port?
Yes, it listens on TCP/IP 2433 and requires encryption. The client libraries
on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problems
connecting to it. It is only the Management Studio that makes me ...
aaarrrgh.
Any ideas?
Adrian

>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Adrian wrote:
> Yes, it listens on TCP/IP 2433 and requires encryption. The client libraries
> on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problems
> connecting to it. It is only the Management Studio that makes me ...
> aaarrrgh.
> Any ideas?
>
In the connection dialog in Management Studio, try specifying the server
name like this:
serverDNSname,2433
And in the Options of that connection dialog, make sure the "Encrypt
Connection" checkbox is marked...
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Managing 2000 and 2005

Dear all
I have now a default instance of SQL Server 2005 running on one PC and an
old default instance of SQL Server 2000 running on another PC.
I would like to administer both SQL Servers with the new SQL Server 2005
Management Studio. However, I am unable to register the SQL Server 2000 in
the SQL Server 2005 Management Studio.
Any help is appreciated.
Best regards
AdrianYou should be able to.
What problems are you seeing?
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>|||Adrian wrote:
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>
"Unable to register" means what exactly? Are you getting an error
message? Management Studio is perfectly capable of working with a 2000
server, I do it all day long every day...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525017F.8020007@.realsqlguy.com...
> Adrian wrote:
> "Unable to register" means what exactly? Are you getting an error
> message? Management Studio is perfectly capable of working with a 2000
> server, I do it all day long every day...
Well, it is great to hear it. So I just need to figure out how.
I can connect to the SQL Server 2000 with the sqlcmd program within an eye's
blink. However, when I enter precisely the same connect data to the
register-dialog of the Management Studio it returns after quite a long time
a message with the error 10061.
So what am I doing wrong?
Adrian

>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||You should be able to connect to a SQL Server 2000 box from the SQL Server
2005 tools (including SSMS, Profiler, and the Replication Monitor
(sqlmonitor).
Keith Kratochvil
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>|||Adrian wrote:
> Well, it is great to hear it. So I just need to figure out how.
> I can connect to the SQL Server 2000 with the sqlcmd program within an eye
's
> blink. However, when I enter precisely the same connect data to the
> register-dialog of the Management Studio it returns after quite a long tim
e
> a message with the error 10061.
> So what am I doing wrong?
That error indicates that the connection was refused by the server. Is
SQL Server using TCP/IP? Listening on what port?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45250DE5.8030609@.realsqlguy.com...
> Adrian wrote:
> That error indicates that the connection was refused by the server. Is
> SQL Server using TCP/IP? Listening on what port?
Yes, it listens on TCP/IP 2433 and requires encryption. The client libraries
on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problems
connecting to it. It is only the Management Studio that makes me ...
aaarrrgh.
Any ideas?
Adrian

>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Adrian wrote:
> Yes, it listens on TCP/IP 2433 and requires encryption. The client librari
es
> on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problem
s
> connecting to it. It is only the Management Studio that makes me ...
> aaarrrgh.
> Any ideas?
>
In the connection dialog in Management Studio, try specifying the server
name like this:
serverDNSname,2433
And in the Options of that connection dialog, make sure the "Encrypt
Connection" checkbox is marked...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Firewalls?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Deal all
Thank you very much for the excellent and very quick help.
Yes, the connection is established.
The trick is:
i) to follow this advice:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
but
ii) not to follow this one:
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
Now my sleep will be peaceful.
Best regards
Adrian
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Managing 2000 and 2005

Dear all
I have now a default instance of SQL Server 2005 running on one PC and an
old default instance of SQL Server 2000 running on another PC.
I would like to administer both SQL Servers with the new SQL Server 2005
Management Studio. However, I am unable to register the SQL Server 2000 in
the SQL Server 2005 Management Studio.
Any help is appreciated.
Best regards
AdrianYou should be able to.
What problems are you seeing?
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>|||Adrian wrote:
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>
"Unable to register" means what exactly? Are you getting an error
message? Management Studio is perfectly capable of working with a 2000
server, I do it all day long every day...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525017F.8020007@.realsqlguy.com...
> Adrian wrote:
>> Dear all
>> I have now a default instance of SQL Server 2005 running on one PC and an
>> old default instance of SQL Server 2000 running on another PC.
>> I would like to administer both SQL Servers with the new SQL Server 2005
>> Management Studio. However, I am unable to register the SQL Server 2000
>> in the SQL Server 2005 Management Studio.
>> Any help is appreciated.
>> Best regards
>> Adrian
> "Unable to register" means what exactly? Are you getting an error
> message? Management Studio is perfectly capable of working with a 2000
> server, I do it all day long every day...
Well, it is great to hear it. So I just need to figure out how.
I can connect to the SQL Server 2000 with the sqlcmd program within an eye's
blink. However, when I enter precisely the same connect data to the
register-dialog of the Management Studio it returns after quite a long time
a message with the error 10061.
So what am I doing wrong?
Adrian
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||You should be able to connect to a SQL Server 2000 box from the SQL Server
2005 tools (including SSMS, Profiler, and the Replication Monitor
(sqlmonitor).
--
Keith Kratochvil
"Adrian" <adrian@.iai.uni-bonn.de> wrote in message
news:Ofpo5yH6GHA.4620@.TK2MSFTNGP02.phx.gbl...
> Dear all
> I have now a default instance of SQL Server 2005 running on one PC and an
> old default instance of SQL Server 2000 running on another PC.
> I would like to administer both SQL Servers with the new SQL Server 2005
> Management Studio. However, I am unable to register the SQL Server 2000 in
> the SQL Server 2005 Management Studio.
> Any help is appreciated.
> Best regards
> Adrian
>|||Adrian wrote:
> Well, it is great to hear it. So I just need to figure out how.
> I can connect to the SQL Server 2000 with the sqlcmd program within an eye's
> blink. However, when I enter precisely the same connect data to the
> register-dialog of the Management Studio it returns after quite a long time
> a message with the error 10061.
> So what am I doing wrong?
That error indicates that the connection was refused by the server. Is
SQL Server using TCP/IP? Listening on what port?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45250DE5.8030609@.realsqlguy.com...
> Adrian wrote:
>> Well, it is great to hear it. So I just need to figure out how.
>> I can connect to the SQL Server 2000 with the sqlcmd program within an
>> eye's blink. However, when I enter precisely the same connect data to the
>> register-dialog of the Management Studio it returns after quite a long
>> time a message with the error 10061.
>> So what am I doing wrong?
> That error indicates that the connection was refused by the server. Is
> SQL Server using TCP/IP? Listening on what port?
Yes, it listens on TCP/IP 2433 and requires encryption. The client libraries
on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problems
connecting to it. It is only the Management Studio that makes me ...
aaarrrgh.
Any ideas?
Adrian
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Adrian wrote:
> Yes, it listens on TCP/IP 2433 and requires encryption. The client libraries
> on the SQL Server 2005 PC are set appriopriately, so sqlcmd has no problems
> connecting to it. It is only the Management Studio that makes me ...
> aaarrrgh.
> Any ideas?
>
In the connection dialog in Management Studio, try specifying the server
name like this:
serverDNSname,2433
And in the Options of that connection dialog, make sure the "Encrypt
Connection" checkbox is marked...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Firewalls?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
>> Yes, it listens on TCP/IP 2433 and requires encryption. The client
>> libraries on the SQL Server 2005 PC are set appriopriately, so sqlcmd has
>> no problems connecting to it. It is only the Management Studio that makes
>> me ... aaarrrgh.
>> Any ideas?
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Deal all
Thank you very much for the excellent and very quick help.
Yes, the connection is established.
The trick is:
i) to follow this advice:
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
but
ii) not to follow this one:
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
Now my sleep will be peaceful.
Best regards
Adrian
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:4525139C.1010502@.realsqlguy.com...
> Adrian wrote:
>> Yes, it listens on TCP/IP 2433 and requires encryption. The client
>> libraries on the SQL Server 2005 PC are set appriopriately, so sqlcmd has
>> no problems connecting to it. It is only the Management Studio that makes
>> me ... aaarrrgh.
>> Any ideas?
> In the connection dialog in Management Studio, try specifying the server
> name like this:
> serverDNSname,2433
> And in the Options of that connection dialog, make sure the "Encrypt
> Connection" checkbox is marked...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com