Volte

Make wType an Int32 rather than a Long, and make it return an Int32 as well.

[api]MessageBeep[/api] API.

I see what you mean now. D'oh. Yes, you need to put the code to increase the Value property in a Timer.

So change the Value property, and the progress bar (the "blue things") will move.

Ah, I didn't think of that. Indeed that would be the quickest.

Yes. When you set the Value property.

Set the Value property.

What do you mean what is the code? You could do this: Dim pb As New ProgressBar() pb.Location = New Point(10, 10) pb.Size = New Size(300, 15) pb.Max = 100 pb.Min = 1 Me.Controls(pb)To add the control manually. I still don't know exactly what you mean though. BTW, Use Shell under VB6.

I would say it most likely is the quickest.

You need to set an alias for the COUNT.SELECT COUNT(id) AS rowcount FROM mytable WHERE id = 7Then use 'rowcount' as if it was a regular field.

1) Put a ProgressBar control on your form. It's in the toolbox. 2) Process.Start("C:\myfile.exe")

Did you name your project "Form" or something?

The 'EDIT' refers to the window class, not the name given in VB. When compiled, the name given by VB is lost (as far as I know, at least). You should set the classname to "WindowsForms10.EDIT.app1" and try that.

Where'd you get your copy of .NET? Is it the Professional edition? I have .NET 2002, but mine contains: <?xml version='1.0' encoding="utf-8" ?> <DynamicHelp xmlns="http://microsoft.com/vstudio/tbd/vsdh.xsd"> <Preference AttrName="Locale" AttrValue="kbEnglish"/> <LINKGROUP ID="help" Title="Help" Priority="500"> <GLYPH Expanded="vs:/ctxhelp_show.gif" Collapsed="vs:/ctxhelp_hide.gif"/> </LINKGROUP> <LINKGROUP ID="actions" Title="Actions" Priority="1000"> <GLYPH Expanded="vs:/ctxwiz_show.gif" Collapsed="vs:/ctxwiz_hide.gif"/> </LINKGROUP> <LINKGROUP ID="misc" Title="Miscellaneous" Priority="10"> <GLYPH Expanded="vs:/ctxmsc_show.gif" Collapsed="vs:/ctxmsc_hide.gif"/> </LINKGROUP> <LINKGROUP ID="samples" Title="Samples" Priority="400"> <GLYPH Expanded="vs:/ctxsample_show.gif" Collapsed="vs:/ctxsample_hide.gif"/> </LINKGROUP> <LINKGROUP ID="GettingStarted" Title="Getting Started" Priority="300"> <GLYPH Expanded="vs:/ctxhelp_show.gif" Collapsed="vs:/ctxhelp_hide.gif"/> </LINKGROUP> </DynamicHelp>

That wouldn't work, assuming Mainid is a number. Single quotes are for strings. I suggest putting the following line about the conflicting line: System.Diagnostics.Debug.WriteLine "DELETE * FROM Daily WHERE Mainid = " & intmainAnd see what it prints in the debug window.

UInt32 is not CLR-compliant and should not be used. Instead, Int64 (Long) should be used. However, if you have no control over it:Dim num As UInt32 = Convert.ToUInt32(<your number>)That should do the trick.

I won't even get started on how much I dislike #develop (for a multitude of reasons), but maybe you could say which errors?

I would suggest reinstalling.

What do the contents of the file mentioned look like?

If you want to spawn the console app from within the other Windows app, you can use the StartInfo property of the Process class (more specifically, StartInfo.RedirectStandardOutput) to tell it to write all its input to the StandardOutput stream of the Process object. Then you can do with it what you want to get the output.

I don't have a reason to ever use C++.NET -- if you want simplicity, use C# or VB.NET. If you want raw power, use C++. I don't see the use in C++.NET which both removes the simplicity from .NET and adds large dependency to C++. My opinion of course.

That's the size they are in VB6 too. In C++ they are 8 bits. Worrying about the size of varaibles is silly, since you have millions of bytes available to you. An extra one byte per boolean won't make a noticable difference.

IIS 4 comes with Windows 2000. If you don't have 2K or higher, you can't use the .NET IDE anyway, so it really doesn't matter. However, if you have Windows 2K+, IIS is on the CD.

How is that old fasioned? That is the only way to do it (short of MFC, but that's a whole other ballgame). And since the intellisence in C++ is based entirely on the definitions of functions, as long as you've #included the proper headers, the Intellisense should be there. I think Squirm had the problem of getting no intellisense at one point, so you may wish to talk to him.

[mshelp]ms-help://MS.VSCC/MS.MSDNVS/vbcn7/html/vaconCallingWindowsAPIs.htm[/mshelp]