"Bill Youngman" <wyoung***@anexinet.com> wrote in message
news:OU6Ffj1pGHA.4424@TK2MSFTNGP05.phx.gbl...
>I have just taken over a project for my current client and have noticed
>several places in the existing application where the developer set the sql
>parameter dbtype to nvarchar in the application code but the field in the
>backend database is a varchar. What effect, if any can this have on the
>application?
>
> TIA,
> Bill Youngman
>

"Arnie Rowland" <ar***@1568.com> wrote in message
news:%23SSSX71pGHA.1440@TK2MSFTNGP03.phx.gbl...
> As long as the application is not using double byte characters (unicode),
> you will be ok. If the application is ever globalized to allow unicode
> dependent languages, there will be a problem to resolve.
>
> For 'peace of mind', I would start making the changes when they are
> discovered -either in the app or the sproc.
>
> --
> Arnie Rowland*
> "To be successful, your heart must accompany your knowledge."
>
>
>
> "Bill Youngman" <wyoung***@anexinet.com> wrote in message
> news:OU6Ffj1pGHA.4424@TK2MSFTNGP05.phx.gbl...
>>I have just taken over a project for my current client and have noticed
>>several places in the existing application where the developer set the sql
>>parameter dbtype to nvarchar in the application code but the field in the
>>backend database is a varchar. What effect, if any can this have on the
>>application?
>>
>> TIA,
>> Bill Youngman
>>
>
>