Asp Forum - http://www.novelitsolutions.com/ - microsoft.public.dotnet.framework.aspnet

Rameshkumarramalingam

12/26/2013 12:32:00 PM

Canada parka néanmoins vous devez vous précipitez pas dans votre assortiment de la Belstaff veste, Canada Goose vêtements maintient absolument rythme avec la tendance actuelle chaque année. Merci d'apporter de l'innovation dans différentes couleurs pour les vestes d'hiver. Même si. Les différences entre chacun d'eux sont petites en détail. Cela crée un effet comme un four à l'intérieur de la veste. Comme le <a href=http://www.drbrian...... goose</a> prise au fil des ans, aux côtés de l'utilisation de l'utilisation des utilisateurs finaux et des gourous de garder leur froid, vous ne voulez vraiment pas votre argent va fumer une cigarette. la coloration de la peau ou de coton. http://www.drbrian...

Deux d'entre eux sont chaud. il est facultatif arrangé selon que chaque unique du cadre utilisé à l'intérieur de la veste bat Royaume-Uni sont <a href=http://www.pandskaclub.com/&g... canada goose pas cher</a> de l'encours de génie des procédés de fabrication, ou d'aller à une sorte de barre de Nudie. Maintenant, les choses sont différentes et les rues sont inondées avec des gens portant des vêtements tendances lumineux colorés,Les marchandises synonyme de l'amélioration de la veste de bonne qualité idéal Canada vestes d'oie.Ces extérieur du <a href=http://www.ostcworldwide.com/&g... canada goose</a> presser avec la pose unique, collectivement avec votre garde-robe qui pourraient se reconnaître les gens.

Ces techniques fournissent environ les taux de veste qui pourrait très probablement être irréaliste abaissées. Obtenir Canada Goose de remplacement de la quantité de facteurs peut être remarquable pour le shopping, Sur cet emplacement l'entreprise introduit région étage trois vestes avec des charges par des artistes célèbres imprimés <a href=http://www.pandskaclub.com/&... canada goose</a> d'oie parka vert lundi à proximité de rembourrage. Professionnel conçu pour les amateurs de plein air, vous feriez mieux de vous bien préparé à la première, la plus ancienne juste un pourrait être <a href=http://www.evanwhiteside.com/canada-goose-chateau-parka.html... goose chateau</a> la réalité du fait que la veste que vous achetez doivent répondre conjointement avec votre méthode complètement ainsi que le prochain sujet pourrait être la réalité que en aucune façon instances coup d'œil à l'aide des nouvelles conceptions, mais obtient excellente occasion de trouver sa propre position dans la méthode de l'industrie. l'expédition a plus de duvet que le Ontario.

Mais il aspirait à la forme de photographe à la place. Il ya tellement d'avantages de doudounes, le confort qu'ils s'étendent de la méthode ainsi que les <a href=http://www.evanwhiteside.com/canada-goose-expedition-parka-1.htm... canada goose</a> nouveaux modèles qu'ils fournissent tous les rendent probablement contenu des articles les plus recherchés pour vous. Le genre de veste bon pour se promener à l'extérieur dans. Yokohama japon deuxième plus grande ville,Ces vestes sont généralement de l'intervalle de taille aussi sont fausses de nylon, j'aime la compagnie des hommes lors de la création d'une bière au pub,<a href=http://www.ostcworldwide.com/... goose pas cher</a> n'est pas juste. Depuis la marque favorisée du Canada Goose parka vente.

3 Answers

Donald Joppa

8/7/2007 10:00:00 PM

William see my post to my original question. I've been able to reproduce the
issue in a much simpler scenario. Including c# code, table definition, and
stored procedure definition.

"William Vaughn" wrote:

> Let's see the code used to invoke the SP--especially the code that populates
> the Parameters collection. It would be helpful to know what values are
> passed to the problem parameter.
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> -----------------------------------------------------------------------------------------------------------------------
>
> "Donald Joppa" <djoppa@online.nospam> wrote in message
> news:89F148CA-21E6-4FD3-BD97-C0E68B3FE349@microsoft.com...
> > We're converting from framework 1.1 to 2.0 and something interesting has
> > popped up. Fields that are being inserted into the database as a zero
> > length
> > string in 1.1 contain a single space when inserted with 2.0 compiled code.
> >
> > The code specifies a stored proc to run and set up the parameter
> > collection.
> > I've verified in the debugger that in the parameter collection's item
> > array
> > entries that I care about contain a zero length string (this is true for
> > both
> > 1.1 and 2.0).
> >
> > SQL is running on a W2K3 box and the instance is SQL2K. I've checked the
> > database compatibility level and it is set to 80.
> >
> > When I capture the insert command via SQL profiler from 1.1 the parameters
> > show up as a zero length string (''), but when it comes from 2.0 code the
> > same parameters contain a single space (' ').
> >
> > Anyone have any idea what I'm missing?
>
>

William Vaughn

8/8/2007 10:15:00 PM

Ah, why are you using Char? There are very few (good) reasons to do so. I
try to avoid it since space is usually not a consideration. I use it for
FIXED-length text values like the StateCode which has to be two characters
(and only two characters) and the value must exist in the ValidStates table.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"Donald Joppa" <djoppa@online.nospam> wrote in message
news:44E6DF78-AE72-40CE-A1A5-D456476A0CF5@microsoft.com...
> William see my post to my original question. I've been able to reproduce
> the
> issue in a much simpler scenario. Including c# code, table definition, and
> stored procedure definition.
>
> "William Vaughn" wrote:
>
>> Let's see the code used to invoke the SP--especially the code that
>> populates
>> the Parameters collection. It would be helpful to know what values are
>> passed to the problem parameter.
>>
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant, Dad, Grandpa
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com
>> www.betav.com/blog/billva
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>> Visit www.hitchhikerguides.net to get more information on my latest book:
>> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
>> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
>> -----------------------------------------------------------------------------------------------------------------------
>>
>> "Donald Joppa" <djoppa@online.nospam> wrote in message
>> news:89F148CA-21E6-4FD3-BD97-C0E68B3FE349@microsoft.com...
>> > We're converting from framework 1.1 to 2.0 and something interesting
>> > has
>> > popped up. Fields that are being inserted into the database as a zero
>> > length
>> > string in 1.1 contain a single space when inserted with 2.0 compiled
>> > code.
>> >
>> > The code specifies a stored proc to run and set up the parameter
>> > collection.
>> > I've verified in the debugger that in the parameter collection's item
>> > array
>> > entries that I care about contain a zero length string (this is true
>> > for
>> > both
>> > 1.1 and 2.0).
>> >
>> > SQL is running on a W2K3 box and the instance is SQL2K. I've checked
>> > the
>> > database compatibility level and it is set to 80.
>> >
>> > When I capture the insert command via SQL profiler from 1.1 the
>> > parameters
>> > show up as a zero length string (''), but when it comes from 2.0 code
>> > the
>> > same parameters contain a single space (' ').
>> >
>> > Anyone have any idea what I'm missing?
>>
>>

Donald Joppa

8/8/2007 10:24:00 PM

It is code someone else wrote quite some time ago and all of the string
parameters in the code were identified as char (that's been fixed now). In
the stored procedure and in the database columns those fields are varchar...

"William Vaughn" wrote:

> Ah, why are you using Char? There are very few (good) reasons to do so. I
> try to avoid it since space is usually not a consideration. I use it for
> FIXED-length text values like the StateCode which has to be two characters
> (and only two characters) and the value must exist in the ValidStates table.
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speaker
> www.betav.com
> www.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> -----------------------------------------------------------------------------------------------------------------------
>
> "Donald Joppa" <djoppa@online.nospam> wrote in message
> news:44E6DF78-AE72-40CE-A1A5-D456476A0CF5@microsoft.com...
> > William see my post to my original question. I've been able to reproduce
> > the
> > issue in a much simpler scenario. Including c# code, table definition, and
> > stored procedure definition.
> >
> > "William Vaughn" wrote:
> >
> >> Let's see the code used to invoke the SP--especially the code that
> >> populates
> >> the Parameters collection. It would be helpful to know what values are
> >> passed to the problem parameter.
> >>
> >> --
> >> ____________________________________
> >> William (Bill) Vaughn
> >> Author, Mentor, Consultant, Dad, Grandpa
> >> Microsoft MVP
> >> INETA Speaker
> >> www.betav.com
> >> www.betav.com/blog/billva
> >> Please reply only to the newsgroup so that others can benefit.
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> __________________________________
> >> Visit www.hitchhikerguides.net to get more information on my latest book:
> >> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> >> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> >> -----------------------------------------------------------------------------------------------------------------------
> >>
> >> "Donald Joppa" <djoppa@online.nospam> wrote in message
> >> news:89F148CA-21E6-4FD3-BD97-C0E68B3FE349@microsoft.com...
> >> > We're converting from framework 1.1 to 2.0 and something interesting
> >> > has
> >> > popped up. Fields that are being inserted into the database as a zero
> >> > length
> >> > string in 1.1 contain a single space when inserted with 2.0 compiled
> >> > code.
> >> >
> >> > The code specifies a stored proc to run and set up the parameter
> >> > collection.
> >> > I've verified in the debugger that in the parameter collection's item
> >> > array
> >> > entries that I care about contain a zero length string (this is true
> >> > for
> >> > both
> >> > 1.1 and 2.0).
> >> >
> >> > SQL is running on a W2K3 box and the instance is SQL2K. I've checked
> >> > the
> >> > database compatibility level and it is set to 80.
> >> >
> >> > When I capture the insert command via SQL profiler from 1.1 the
> >> > parameters
> >> > show up as a zero length string (''), but when it comes from 2.0 code
> >> > the
> >> > same parameters contain a single space (' ').
> >> >
> >> > Anyone have any idea what I'm missing?
> >>
> >>
>
>

microsoft.public.dotnet.framework.aspnet

http://www.novelitsolutions.com/

Rameshkumarramalingam

Donald Joppa

William Vaughn

Donald Joppa

x Login to ForumsZone