Item 1 above clearly shows why an ejumicatsun is imperative. Had he had the smarts ahead of time, he would have attended a state college and could have been trained in all kinds of stuff he'll never use for a lot less than $100k. It should have been $60k tops. And that's for good quality stuff...
That's the key to anything.... use the right tool for the right job for the right reason. In the case of a grid of parents, which when clicked will display child records else where, then it makes sense. BUT.... in the case of our current app, that wouldn't work because it isn't grid based. A...
You creates s as a string in the loop.... but then try to use it as the index value to the array (which is expecting an integer, not a string).... Since s already has the text from the pathList.... it should be this:
x.ExtractZip(s, strFullDirectoryPath, "csv;xsl")
ick, that's the VB6 compatibly talking there.... preferred method is Environment.NewLine.
Dude, that's so old school... welcome to the 2000's! And FYI... a carriage return simply returns to the front of the line.... well, it's supposed to... it's the newline (chr(10)) that actually moves to the...
for nchar and char fields... yes... those are fixed length fields..... if you want variable lengths, use nvarchar or varchar.
edit: if you .Trim what comes from SQL, the trailing spaces will be trimmed.
Building upon cjard's lesson there, the reason for this is that strings are what is called "immutable". Meaning they cannot change. Once they are set, that's it. You are probably now going "Wait a minute! But... But..." When you concatenate strings together, what really happens is that a NEW...
TRy changing it to this:
If pass.Equals(compare) Then ....
In addition, by default... it is case sensitive. IE, "ThisPassword" is not the same as "THISPASSWORD" ... the Equals has a second parameter that you can send in to tell it to ignore the case.
If that doesn't work, look at the...
Your logic is wrong....
You've told it to see if item 3 is null ..... and item is not null..... so if both are filled in, or even if just item 3 is filled in, you get your messagebox.
What you really want is this:
If Not (objReader.IsDBNull(3) And objReader.IsDBNull(4)) Then
Look at the server object..... I vaguely remember comming across a method ClearPool or it might have been PoolingClear.... something to that effect. I thought of this thread when I found it, but wasn't in a position to reply.
USe a SELECT DISTINCT to select all the unique rows in your table.... insert the data into a new table, preferably one that has a PK on it.... drop the old table. Rename the new table to the same as the old table.