Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Not exact match
Message
From
19/11/2003 19:10:01
 
 
To
All
General information
Forum:
ASP.NET
Category:
Other
Title:
Not exact match
Miscellaneous
Thread ID:
00851689
Message ID:
00851689
Views:
52
I have this code which detects for a specific error message:
      Catch loError As Exception
         lcError = loError.Message
         Select Case lcError
            Case "Bad Data"
               lcError = "You didn't encrypt the XML string with a valid key."
         End Select
         Return lcError
      End Try
However, as the Case is doing an exact match, it doesn't find a match when Bad Data is returned as the correct string is Bad Data + 3 characters. I don't want to have to deal with the 3 extra characters nor having the removal procedures I had before. How can I make this Case to be not sensitive about the string? Basically, if it starts with Bad Data, this is all I need.
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Next
Reply
Map
View

Click here to load this message in the networking platform