Board index » Visual Studio » Why this warning in IDE?

Why this warning in IDE?

Visual Studio287
Dim Myfiles() as string

Myfiles(0) = "filename1"

I get a warning on line myfiles(0)=.. that myfiles has been used before it

has been assigned a value a null exception may occur. Obviously this is bs,

since I am in the process of assigning a value at that instant in code. How

do I prevent this warning from appearing? Maybe I should code this in a

different way?



Any help would be appreciated.

Bob


-
 

Re:Why this warning in IDE?



rdufour napisal(a):

Quote
Dim Myfiles() as string

Myfiles(0) = "filename1"

I get a warning on line myfiles(0)=.. that myfiles has been used before it

has been assigned a value a null exception may occur. Obviously this is bs,

since I am in the process of assigning a value at that instant in code. How

do I prevent this warning from appearing? Maybe I should code this in a

different way?



Any help would be appreciated.

Bob



Bob,



You get this warning because you haven't set size of array MyFiles. If

you do this you won't get worning.



Regards,

sweet_dreams



-

Re:Why this warning in IDE?

Dim Myfiles(upperArrayBoundry) As String







"rdufour" <bdufour@sgiims.com>wrote in message

Quote
Dim Myfiles() as string

Myfiles(0) = "filename1"

I get a warning on line myfiles(0)=.. that myfiles has been used before it

has been assigned a value a null exception may occur. Obviously this is

bs, since I am in the process of assigning a value at that instant in

code. How do I prevent this warning from appearing? Maybe I should code

this in a different way?



Any help would be appreciated.

Bob









-

Re:Why this warning in IDE?



Dim Myfiles() as string={"filename1","filename2","filename3"}



regards



Michel







"rdufour" <bdufour@sgiims.com>schreef in bericht

Quote
Dim Myfiles() as string

Myfiles(0) = "filename1"

I get a warning on line myfiles(0)=.. that myfiles has been used before it

has been assigned a value a null exception may occur. Obviously this is

bs, since I am in the process of assigning a value at that instant in

code. How do I prevent this warning from appearing? Maybe I should code

this in a different way?



Any help would be appreciated.

Bob









-