reserved word for DB column name crashes data adapter update

[Benoit Martin]

I'm working on a project in VB.net connecting to a SQL Server 2000 database
that I can't modify
I created a dataset with a schema identical to the DB.
When trying to update the DB from the dataset using the dataAdapter.upd ate
sub, I get an error.
The problem seems to be that one of the fields was named 'desc' which is a
reserved word for SQL.
I've been able to work around this design flaw 'till now but it looks like
the update sub can't handle it.
I used the command builder to create the Update, Insert and Delete scripts.
The trace is like this:

An unhandled exception of type 'System.Data.Sq lClient.SqlExce ption' occurred
in system.data.dll

Additional information: System error.
Unhandled Exception: System.Data.Sql Client.SqlExcep tion: Incorrect syntax
near the keyword 'desc'.
at System.Data.Com mon.DbDataAdapt er.Update(DataR ow[] dataRows,
DataTableMappin g tableMapping)
at System.Data.Com mon.DbDataAdapt er.Update(DataT able dataTable)

Is there a way around this?

[Mike Labosh]

> I'm working on a project in VB.net connecting to a SQL Server 2000
database

that I can't modify
I created a dataset with a schema identical to the DB.
When trying to update the DB from the dataset using the dataAdapter.upd ate
sub, I get an error.
If you cannot modify the database, why bother trying to update it? This
would be my first red flag.
I've been able to work around this design flaw 'till now but it looks like
the update sub can't handle it.

Every once in a while, someone makes a column or other object in a database
whose name is a reserved word. SQL Server will let you refer to this if you
enclose the object's identifier in square brackets:

SELECT [Desc] FROM t_SomeTable

Sometimes, SQL Server will understand what you mean if you qualify the item
you are referring to:

SELECT t_SomeTable.Des c FROM t_SomeTable

Another thing you might consider, though I personally don't like it is this:

SET QUOTED_IDENTIFI ER ON
SELECT "Desc" FROM t_SomeTable
SET QUOTED_IDENTIFI ER OFF

Generally speaking, the SQL Server Query Analyzer is your best friend for
figuring out correct SQL syntax irrespective of application code. Once you
get the SQL syntax to do the right thing in Query Analyzer, then try it in
your application code. If it then doesn't work, there is something else
going wrong, such as runtime permissions or other screwy application stuff.
--
Peace & happy computing,

Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei

[Benoit Martin]

when I said that I can't modify the DB, I meant the structure, not the data.

I was aware of the [] work around but it doesn't look like VB.net does it.
The update code is generated by VB.net as I used the command builder (don't
waste your time telling me that I should write my own instead of using the
command builder)
It looks like if you use a reserved word, VB.net will not take any
precautions to avoid an error when dealing with the database.

Is there a way to correct that problem?

"Mike Labosh" <ml************ *****@vbsensei. com> wrote in message
news:ur******** ******@TK2MSFTN GP11.phx.gbl...

I'm working on a project in VB.net connecting to a SQL Server 2000 database

that I can't modify
I created a dataset with a schema identical to the DB.
When trying to update the DB from the dataset using the dataAdapter.upd ate sub, I get an error.

If you cannot modify the database, why bother trying to update it? This
would be my first red flag.

I've been able to work around this design flaw 'till now but it looks like the update sub can't handle it.

Every once in a while, someone makes a column or other object in a

database whose name is a reserved word. SQL Server will let you refer to this if you enclose the object's identifier in square brackets:

SELECT [Desc] FROM t_SomeTable

Sometimes, SQL Server will understand what you mean if you qualify the item you are referring to:

SELECT t_SomeTable.Des c FROM t_SomeTable

Another thing you might consider, though I personally don't like it is this:
SET QUOTED_IDENTIFI ER ON
SELECT "Desc" FROM t_SomeTable
SET QUOTED_IDENTIFI ER OFF

Generally speaking, the SQL Server Query Analyzer is your best friend for
figuring out correct SQL syntax irrespective of application code. Once you get the SQL syntax to do the right thing in Query Analyzer, then try it in
your application code. If it then doesn't work, there is something else
going wrong, such as runtime permissions or other screwy application stuff. --
Peace & happy computing,

Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei

[William Ryan]

Benoit:

If there's a battle worth fighting, it's Changing column names that are
reserved words. Have you tried changing the Alias on it w/ the []? I've
been told by many that it should work unless you are using access. If you
can't do any of that, why not create a View based on the table and give it
real names. Whoever insists on using Desc and not letting you change it is
being Very shortsighted, but he/she couldn't possibly prohibit you from
creating a view and using it instead.
"Benoit Martin" <bm*********@ho tmail.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

when I said that I can't modify the DB, I meant the structure, not the data.
I was aware of the [] work around but it doesn't look like VB.net does it.
The update code is generated by VB.net as I used the command builder (don't waste your time telling me that I should write my own instead of using the
command builder)
It looks like if you use a reserved word, VB.net will not take any
precautions to avoid an error when dealing with the database.

Is there a way to correct that problem?

"Mike Labosh" <ml************ *****@vbsensei. com> wrote in message
news:ur******** ******@TK2MSFTN GP11.phx.gbl...

I'm working on a project in VB.net connecting to a SQL Server 2000

database

that I can't modify
I created a dataset with a schema identical to the DB.
When trying to update the DB from the dataset using the dataAdapter.upd ate sub, I get an error.

If you cannot modify the database, why bother trying to update it? This
would be my first red flag.

I've been able to work around this design flaw 'till now but it looks like the update sub can't handle it.

Every once in a while, someone makes a column or other object in a

database

whose name is a reserved word. SQL Server will let you refer to this if

you

enclose the object's identifier in square brackets:

SELECT [Desc] FROM t_SomeTable

Sometimes, SQL Server will understand what you mean if you qualify the

item

you are referring to:

SELECT t_SomeTable.Des c FROM t_SomeTable

Another thing you might consider, though I personally don't like it is

this:

SET QUOTED_IDENTIFI ER ON
SELECT "Desc" FROM t_SomeTable
SET QUOTED_IDENTIFI ER OFF

Generally speaking, the SQL Server Query Analyzer is your best friend for figuring out correct SQL syntax irrespective of application code. Once

you

get the SQL syntax to do the right thing in Query Analyzer, then try it in your application code. If it then doesn't work, there is something else
going wrong, such as runtime permissions or other screwy application

stuff.

--
Peace & happy computing,

Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei

[Benoit Martin]

thanks William,

not being able to change the field name is not too much a problem of being
stuborn but more a problem with the consequences of changing this field
name.

When you are talking about Alia, is it in the dataset? I wasn't aware of
this alias "property". Where is that set?

Thank you

"William Ryan" <do********@nos pam.comcast.net > wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. .

Benoit:

If there's a battle worth fighting, it's Changing column names that are
reserved words. Have you tried changing the Alias on it w/ the []? I've
been told by many that it should work unless you are using access. If you
can't do any of that, why not create a View based on the table and give it
real names. Whoever insists on using Desc and not letting you change it is being Very shortsighted, but he/she couldn't possibly prohibit you from
creating a view and using it instead.
"Benoit Martin" <bm*********@ho tmail.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

when I said that I can't modify the DB, I meant the structure, not the data.

I was aware of the [] work around but it doesn't look like VB.net does it.

The update code is generated by VB.net as I used the command builder

(don't

waste your time telling me that I should write my own instead of using the command builder)
It looks like if you use a reserved word, VB.net will not take any
precautions to avoid an error when dealing with the database.

Is there a way to correct that problem?

"Mike Labosh" <ml************ *****@vbsensei. com> wrote in message
news:ur******** ******@TK2MSFTN GP11.phx.gbl...

> I'm working on a project in VB.net connecting to a SQL Server 2000
database
> that I can't modify
> I created a dataset with a schema identical to the DB.
> When trying to update the DB from the dataset using the

dataAdapter.upd ate

> sub, I get an error.

If you cannot modify the database, why bother trying to update it? This would be my first red flag.

> I've been able to work around this design flaw 'till now but it looks

like

> the update sub can't handle it.

Every once in a while, someone makes a column or other object in a

database

whose name is a reserved word. SQL Server will let you refer to this

if you

enclose the object's identifier in square brackets:

SELECT [Desc] FROM t_SomeTable

Sometimes, SQL Server will understand what you mean if you qualify the

item

you are referring to:

SELECT t_SomeTable.Des c FROM t_SomeTable

Another thing you might consider, though I personally don't like it is

this:

SET QUOTED_IDENTIFI ER ON
SELECT "Desc" FROM t_SomeTable
SET QUOTED_IDENTIFI ER OFF

Generally speaking, the SQL Server Query Analyzer is your best friend for figuring out correct SQL syntax irrespective of application code.

Once you

get the SQL syntax to do the right thing in Query Analyzer, then try

it in your application code. If it then doesn't work, there is something

else going wrong, such as runtime permissions or other screwy application

stuff.

--
Peace & happy computing,

Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei

[William Ryan]

SELECT SomeColumn as AliasName from MyTable
"Benoit Martin" <bm*********@ho tmail.com> wrote in message
news:Ob******** ******@tk2msftn gp13.phx.gbl...

thanks William,

not being able to change the field name is not too much a problem of being
stuborn but more a problem with the consequences of changing this field
name.

When you are talking about Alia, is it in the dataset? I wasn't aware of
this alias "property". Where is that set?

Thank you

"William Ryan" <do********@nos pam.comcast.net > wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. .

Benoit:

If there's a battle worth fighting, it's Changing column names that are
reserved words. Have you tried changing the Alias on it w/ the []? I've

been told by many that it should work unless you are using access. If you can't do any of that, why not create a View based on the table and give it real names. Whoever insists on using Desc and not letting you change it is

being Very shortsighted, but he/she couldn't possibly prohibit you from
creating a view and using it instead.
"Benoit Martin" <bm*********@ho tmail.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

when I said that I can't modify the DB, I meant the structure, not the

data.

I was aware of the [] work around but it doesn't look like VB.net does it. The update code is generated by VB.net as I used the command builder

(don't

waste your time telling me that I should write my own instead of using the command builder)
It looks like if you use a reserved word, VB.net will not take any
precautions to avoid an error when dealing with the database.

Is there a way to correct that problem?

"Mike Labosh" <ml************ *****@vbsensei. com> wrote in message
news:ur******** ******@TK2MSFTN GP11.phx.gbl...
> > I'm working on a project in VB.net connecting to a SQL Server 2000
> database
> > that I can't modify
> > I created a dataset with a schema identical to the DB.
> > When trying to update the DB from the dataset using the
dataAdapter.upd ate
> > sub, I get an error.
>
> If you cannot modify the database, why bother trying to update it? This > would be my first red flag.
>
> > I've been able to work around this design flaw 'till now but it looks like
> > the update sub can't handle it.
>
> Every once in a while, someone makes a column or other object in a
database
> whose name is a reserved word. SQL Server will let you refer to this if

you
> enclose the object's identifier in square brackets:
>
> SELECT [Desc] FROM t_SomeTable
>
> Sometimes, SQL Server will understand what you mean if you qualify

the item
> you are referring to:
>
> SELECT t_SomeTable.Des c FROM t_SomeTable
>
> Another thing you might consider, though I personally don't like it is this:
>
> SET QUOTED_IDENTIFI ER ON
> SELECT "Desc" FROM t_SomeTable
> SET QUOTED_IDENTIFI ER OFF
>
> Generally speaking, the SQL Server Query Analyzer is your best

friend for

> figuring out correct SQL syntax irrespective of application code.

Once you
> get the SQL syntax to do the right thing in Query Analyzer, then try it

in

> your application code. If it then doesn't work, there is something

else > going wrong, such as runtime permissions or other screwy application
stuff.
> --
> Peace & happy computing,
>
> Mike Labosh, MCSD MCT
> Owner, vbSensei.Com
> "Escriba coda ergo sum." -- vbSensei
>
>

[Benoit Martin]

oh, that's what you were talking about, sorry...

unfortunately I don't think it's gonna work for me as the code is generated
by VB and I don't write any SELECT statement for my update command.

I guess there is no work around then

"William Ryan" <do********@nos pam.comcast.net > wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

SELECT SomeColumn as AliasName from MyTable
"Benoit Martin" <bm*********@ho tmail.com> wrote in message
news:Ob******** ******@tk2msftn gp13.phx.gbl...

thanks William,

not being able to change the field name is not too much a problem of being

stuborn but more a problem with the consequences of changing this field
name.

When you are talking about Alia, is it in the dataset? I wasn't aware of
this alias "property". Where is that set?

Thank you

"William Ryan" <do********@nos pam.comcast.net > wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. .

Benoit:

If there's a battle worth fighting, it's Changing column names that are reserved words. Have you tried changing the Alias on it w/ the []? I've been told by many that it should work unless you are using access. If you can't do any of that, why not create a View based on the table and give

it

real names. Whoever insists on using Desc and not letting you change

it is

being Very shortsighted, but he/she couldn't possibly prohibit you

from creating a view and using it instead.
"Benoit Martin" <bm*********@ho tmail.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
> when I said that I can't modify the DB, I meant the structure, not the data.
>
> I was aware of the [] work around but it doesn't look like VB.net does it.

> The update code is generated by VB.net as I used the command builder
(don't
> waste your time telling me that I should write my own instead of

using the

> command builder)
> It looks like if you use a reserved word, VB.net will not take any
> precautions to avoid an error when dealing with the database.
>
> Is there a way to correct that problem?
>
> "Mike Labosh" <ml************ *****@vbsensei. com> wrote in message
> news:ur******** ******@TK2MSFTN GP11.phx.gbl...
> > > I'm working on a project in VB.net connecting to a SQL Server

2000 > > database
> > > that I can't modify
> > > I created a dataset with a schema identical to the DB.
> > > When trying to update the DB from the dataset using the
> dataAdapter.upd ate
> > > sub, I get an error.
> >
> > If you cannot modify the database, why bother trying to update it? This

> > would be my first red flag.
> >
> > > I've been able to work around this design flaw 'till now but it

looks

> like
> > > the update sub can't handle it.
> >
> > Every once in a while, someone makes a column or other object in a
> database
> > whose name is a reserved word. SQL Server will let you refer to

this

if

> you
> > enclose the object's identifier in square brackets:
> >
> > SELECT [Desc] FROM t_SomeTable
> >
> > Sometimes, SQL Server will understand what you mean if you qualify

the > item
> > you are referring to:
> >
> > SELECT t_SomeTable.Des c FROM t_SomeTable
> >
> > Another thing you might consider, though I personally don't like it is

> this:
> >
> > SET QUOTED_IDENTIFI ER ON
> > SELECT "Desc" FROM t_SomeTable
> > SET QUOTED_IDENTIFI ER OFF
> >
> > Generally speaking, the SQL Server Query Analyzer is your best friend for
> > figuring out correct SQL syntax irrespective of application code.

Once

> you
> > get the SQL syntax to do the right thing in Query Analyzer, then

try it

in
> > your application code. If it then doesn't work, there is

something else

> > going wrong, such as runtime permissions or other screwy

application > stuff.
> > --
> > Peace & happy computing,
> >
> > Mike Labosh, MCSD MCT
> > Owner, vbSensei.Com
> > "Escriba coda ergo sum." -- vbSensei
> >
> >
>
>

[Cor]

Hi Benoit,

Take a look on your form and see if you see there below the OleDBdatadapter
or the SQLdataadapter.

Probably it is there rightclick on it and choose configure adapter, there
you can change your select statement.

I hope this helps

Cor

unfortunately I don't think it's gonna work for me as the code is generated by VB and I don't write any SELECT statement for my update command.

[One Handed Man [ OHM# ]]

Sorry, but I have to step in here. I've been watching this thread with
dubious interest.

You seem to have this idea that command builder is king, well let me tell
you that it is not.
Command builder can only handle simple queries, sooner or later you are
going
to have to roll up your sleeves and get your hands dirty.

Bill' suggestion is a good one, simply modify the code already produced by
the
command builer to suit your needs.

OHM#

Benoit Martin wrote:

oh, that's what you were talking about, sorry...

unfortunately I don't think it's gonna work for me as the code is
generated by VB and I don't write any SELECT statement for my update
command.

I guess there is no work around then

"William Ryan" <do********@nos pam.comcast.net > wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

SELECT SomeColumn as AliasName from MyTable
"Benoit Martin" <bm*********@ho tmail.com> wrote in message
news:Ob******** ******@tk2msftn gp13.phx.gbl...

thanks William,

not being able to change the field name is not too much a problem
of being stuborn but more a problem with the consequences of
changing this field name.

When you are talking about Alia, is it in the dataset? I wasn't
aware of this alias "property". Where is that set?

Thank you

"William Ryan" <do********@nos pam.comcast.net > wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. .
Benoit:

If there's a battle worth fighting, it's Changing column names
that are reserved words. Have you tried changing the Alias on it
w/ the []? I've been told by many that it should work unless you
are using access. If you can't do any of that, why not create a
View based on the table and give it real names. Whoever insists
on using Desc and not letting you change it is being Very
shortsighted, but he/she couldn't possibly prohibit you from
creating a view and using it instead. "Benoit Martin"
<bm*********@ho tmail.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
> when I said that I can't modify the DB, I meant the structure,
> not the data.
>
> I was aware of the [] work around but it doesn't look like VB.net
> does it. The update code is generated by VB.net as I used the
> command builder (don't waste your time telling me that I should
> write my own instead of using the command builder)
> It looks like if you use a reserved word, VB.net will not take any
> precautions to avoid an error when dealing with the database.
>
> Is there a way to correct that problem?
>
> "Mike Labosh" <ml************ *****@vbsensei. com> wrote in message
> news:ur******** ******@TK2MSFTN GP11.phx.gbl...
>>> I'm working on a project in VB.net connecting to a SQL Server
>>> 2000 database that I can't modify
>>> I created a dataset with a schema identical to the DB.
>>> When trying to update the DB from the dataset using the
>>> dataAdapter.upd ate sub, I get an error.
>>
>> If you cannot modify the database, why bother trying to update
>> it? This would be my first red flag.
>>
>>> I've been able to work around this design flaw 'till now but it
>>> looks like the update sub can't handle it.
>>
>> Every once in a while, someone makes a column or other object in
>> a database whose name is a reserved word. SQL Server will let
>> you refer to

this

if
> you
>> enclose the object's identifier in square brackets:
>>
>> SELECT [Desc] FROM t_SomeTable
>>
>> Sometimes, SQL Server will understand what you mean if you
>> qualify the item you are referring to:
>>
>> SELECT t_SomeTable.Des c FROM t_SomeTable
>>
>> Another thing you might consider, though I personally don't like it

is

> this:
>>
>> SET QUOTED_IDENTIFI ER ON
>> SELECT "Desc" FROM t_SomeTable
>> SET QUOTED_IDENTIFI ER OFF
>>
>> Generally speaking, the SQL Server Query Analyzer is your best
>> friend for figuring out correct SQL syntax irrespective of
>> application code. Once you get the SQL syntax to do the right
>> thing in Query Analyzer, then

try it
in
>> your application code. If it then doesn't work, there is
>> something else going wrong, such as runtime permissions or other
>> screwy application stuff. --
>> Peace & happy computing,
>>
>> Mike Labosh, MCSD MCT
>> Owner, vbSensei.Com
>> "Escriba coda ergo sum." -- vbSensei

Regards - OHM# On**********@BT Internet.com

[Cor]

Hi OHM are you sure the OP is using the commandbuilder, this looks like drag
and drop, but I can be wrong.

He says "I dont write any SELECT statement"

Not "I dont write any UPDATE statement"

But maybe I am wrong, and maybe he answer us about that after this message.

Cor

"One Handed Man [ OHM# ]" <te************ *************** @BTOpenworld.co m>
schreef in bericht news:eq******** ******@TK2MSFTN GP09.phx.gbl...

Sorry, but I have to step in here. I've been watching this thread with
dubious interest.

You seem to have this idea that command builder is king, well let me tell
you that it is not.
Command builder can only handle simple queries, sooner or later you are
going
to have to roll up your sleeves and get your hands dirty.

Bill' suggestion is a good one, simply modify the code already produced by
the
command builer to suit your needs.

OHM#

Benoit Martin wrote:

oh, that's what you were talking about, sorry...

unfortunately I don't think it's gonna work for me as the code is
generated by VB and I don't write any SELECT statement for my update
command.

I guess there is no work around then

"William Ryan" <do********@nos pam.comcast.net > wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

SELECT SomeColumn as AliasName from MyTable
"Benoit Martin" <bm*********@ho tmail.com> wrote in message
news:Ob******** ******@tk2msftn gp13.phx.gbl...
thanks William,

not being able to change the field name is not too much a problem
of being stuborn but more a problem with the consequences of
changing this field name.

When you are talking about Alia, is it in the dataset? I wasn't
aware of this alias "property". Where is that set?

Thank you

"William Ryan" <do********@nos pam.comcast.net > wrote in message
news:%2******** *******@tk2msft ngp13.phx.gbl.. .
> Benoit:
>
> If there's a battle worth fighting, it's Changing column names
> that are reserved words. Have you tried changing the Alias on it
> w/ the []? I've been told by many that it should work unless you
> are using access. If you can't do any of that, why not create a
> View based on the table and give it real names. Whoever insists
> on using Desc and not letting you change it is being Very
> shortsighted, but he/she couldn't possibly prohibit you from
> creating a view and using it instead. "Benoit Martin"
> <bm*********@ho tmail.com> wrote in message
> news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
>> when I said that I can't modify the DB, I meant the structure,
>> not the data.
>>
>> I was aware of the [] work around but it doesn't look like VB.net
>> does it. The update code is generated by VB.net as I used the
>> command builder (don't waste your time telling me that I should
>> write my own instead of using the command builder)
>> It looks like if you use a reserved word, VB.net will not take any
>> precautions to avoid an error when dealing with the database.
>>
>> Is there a way to correct that problem?
>>
>> "Mike Labosh" <ml************ *****@vbsensei. com> wrote in message
>> news:ur******** ******@TK2MSFTN GP11.phx.gbl...
>>>> I'm working on a project in VB.net connecting to a SQL Server
>>>> 2000 database that I can't modify
>>>> I created a dataset with a schema identical to the DB.
>>>> When trying to update the DB from the dataset using the
>>>> dataAdapter.upd ate sub, I get an error.
>>>
>>> If you cannot modify the database, why bother trying to update
>>> it? This would be my first red flag.
>>>
>>>> I've been able to work around this design flaw 'till now but it
>>>> looks like the update sub can't handle it.
>>>
>>> Every once in a while, someone makes a column or other object in
>>> a database whose name is a reserved word. SQL Server will let
>>> you refer to
this
if
>> you
>>> enclose the object's identifier in square brackets:
>>>
>>> SELECT [Desc] FROM t_SomeTable
>>>
>>> Sometimes, SQL Server will understand what you mean if you
>>> qualify the item you are referring to:
>>>
>>> SELECT t_SomeTable.Des c FROM t_SomeTable
>>>
>>> Another thing you might consider, though I personally don't like

it

is
>> this:
>>>
>>> SET QUOTED_IDENTIFI ER ON
>>> SELECT "Desc" FROM t_SomeTable
>>> SET QUOTED_IDENTIFI ER OFF
>>>
>>> Generally speaking, the SQL Server Query Analyzer is your best
>>> friend for figuring out correct SQL syntax irrespective of
>>> application code. Once you get the SQL syntax to do the right
>>> thing in Query Analyzer, then

try

it
> in
>>> your application code. If it then doesn't work, there is
>>> something else going wrong, such as runtime permissions or other
>>> screwy application stuff. --
>>> Peace & happy computing,
>>>
>>> Mike Labosh, MCSD MCT
>>> Owner, vbSensei.Com
>>> "Escriba coda ergo sum." -- vbSensei

Regards - OHM# On**********@BT Internet.com