Search:

Explicit conversions... that's why the general recomendation is to set Option Explicit On by default.

-tg

Not automatically... you could even have multiple instances on the same computer... I have three.... SQLEXPRESS, SQLServer200R2 and SQLServer2012 .... I *think* you can use SQL DMO to iterate the...

and now you've introduced a new method: objRk.genericSqlexec(strSQL, objRk._SQLRl) with no mention what it is or what it returns... given that you now have an error that .EOF is not a member of...

WAy I read it is that
SELECT 123 - would be valid
SELECT DatePart(yyyy,GetDate()) -- also valid....
but
SELECT DatePart(yyyy,G3tDate())
wouldn't be? sounds like the value being selected could...

I'd further point out that we're talking about the .Name property control....
Dim myLabel as New Label ... that's not a name... that's just the variable...

yeah... I think we've all been caught...

I tried fixing a car. I inserted herrings with no success...

that's about what I got from the post...

"I had tried a few different things with no success." -- what did you try and what does...

actually to be fair... It IS letting you do it.. .but you're then corrupting explorer... and since explorer.exe is the main UI application for windows... I'm a little surprised that your system is...

interesting thing about events... not only does it send in the event arguments... but it also sends in the control that invoked the event... so in your event handler, you know the control that is the...

I'm jsut trying to figure out what was behind the use of the Parse in the first place... get the current date. lop off 10 days, then use the .ToString method to get the date in a string...

then...

Almost, look again... ParseExact... not Parse ...

-tg

You're right... we screwed up big time... we made the fatal assumption you knew how to write a syntatcally correct select statement. mea culpa... won't happen again.

-tg

"Move will not work across network volumes." -- hmmmm... that's a new one to me... guess I've only ever moved locally.... interesting...

-tg

Arg....
1) that code shouldn't be in the form load event of frmMain
2) that code shouldn't be in the form load event of the child form
3) you missed the most important piece of code... how in blue...

well fullName is going to come out looking like this:
Q:\Archive\\\05.16.13*


which... yeah... is invalid...



Private Sub Button1_Click(sender As System.Object, e As System.EventArgs)...

I wondered about that too... but when I looked at the SQL a little harder, I saw that it's a sequence number based on the client... so an Identity won't work.

-tg

Hmmm.... it would seem that you're setting the MDIParent of the default instance of the form... how are you creating and showing the child forms?

-tg

Step 1 - Read the documentation

-tg

Generally speaking... yes... occasionally though, you have to help it along...

-tg

What check? I don't see any "check" in your code... you're grabbing an entire folder and coping it to a new location, using the date as the folder name...

-tg

wow... then you missed out on the whole point of the article... which is how to use parameters.... funny thing is that using parameters in a select is exactly the same as in an insert or an update......

err.... yeah, what he said.... I didn't even say anyhting about using NOLOCK hint... all that would do is allow you to read uncommitted transactions... its does NOT bypass the READ LOCK that the...

No it's not the same thing... as soon as you unload a form, your Forms.Count drops by one... eventually the loop will hit the end of the array and complain about the index exceeding the bounds of the...

It's your Reader... when you use a reader, it gets an exclusive lock... which can then tie up the tables in the query... you get the time out because it waits for the lock to be released so it can...

It's called the TitleBar... and you set it by setting the Text property of the form as dbasnett showed.

-tg

The key maybe the 5 words that happen after the assembly name ... "or one of its dependencies." ... which means that DevIL.NET2 may be relying on yet more assemblies, which aren't being carried over...

wow... can they do it again?
There is a "transaction" but it's an implied transaction and "commits" as the line runs... it's weird... but the point is that what you're seeing is possible but...

Against my better judgement... I'm going to allow myself to get sucked into this thread for a moment...

what you're looking for is the Dir() function

I'll leave it to you to figure the details....

Personally I don't care for forms that load data in other forms like this... having a "please wait" form is fine... but that's all it should do... it should be generic and do nothing more.... the...

it looks right, but it isn't... first, when you call the onChange event, the function you're calling is expecting a parameter... so you need to supply one... which is where the rest of your problem...

yes... you can use the same parameter name across multiple methods... one has nothing to do with the other... it's just a name.

-tg

Yeah, GO won't work inside of an sproc... outside of it, it works great... and you don't need to use transactions with Try/Catch... but it could be used in a stored proc to prevent errors from...

it's defined right there... it's the name of the parameter... it's just like any other method you would create in VB... I'm not sure what the disconnect is, except that you may have issues with the...

Huh? What do you mean no variable name is given? retval is the variable name... from the DLL side... from the VB side, you pass it any Long variable you want... Oh... wait... that's a C long isn't...

More likely it was the drivers doing it than VB6 itself... but yes, the users shouldn't be fiddling about with the DB like that... and if they are, that's like breaking the seal and voiding the...

well, since you can't have a GO in the middle of a stored proc (at least not that I'm aware of... I've always used the GO at the end, signifying the end of the SP) it's kind of moot... but in these...

meaning that the calls between the commands aren't persisting... so if I do a "cd \cmd" ... it does... but the window (the hidden cmd one) doesn't stick around, so if I then try to run a file in that...

Check to make sure that SQLServer Express has been installed... AND that the default named instance is correct... what you left out in the error message was the next sentence... "The server was not...

"If "Allow Zero Length=No" then an empty string is allowed but null isnt." --- that sounds backwards...

a zero-length string would be an empty string... which is not the same as a null. you can...

there's nothing wrong with the com object... at least there wouldn't be if you actually instanciated it... you declared calcul as a tesxting_COM.Class1 ... that's fine... but you never created the...

you only use SET when SETting an object... the .get_ChannelNo is a property that returns a long... not an object... so there's no need to SET the variable...

-tg