Visual Basic

Hello, Here's a good VB site that has ZIPs of MS icons plus some win 200 icons. I think its just what you are looking for. http://www.vbaccelerator.com/ http://www.vbaccelerator.com/iconlib.htm There's lots of good VB code also, check it out! -- Marty

Maybe this can help you... http://support.microsoft.com/support/kb/articles/Q113/9/57.asp -Øyvind

You didn't say what version of Word you're using, but in general, the answer to your question is YES! The best approach is to write a COM Add-In in Visual Basic and then ensure that the add-in loads on startup in Word. Within the code of the add-in, you'll want to hook into the CommandBars collection. Within this collection, you can access existing buttons, or you can create your own using the add method. Then, you'll create an event sink, you that you get access the the click event of the new (or existing) button. There a lot of good documentation about this on MSDN Online. Hope this helps! Jase

if you in WINNT or WIN2k You can use Shell command Net Share

Nope. Not the kodak thumbnail. I'm talking about the one in the dll webvw.dll (under system32). I have gotten answer from Microsoft that this control is not for public usage... this sucks! it only works when being accesses by a specific control (being Internet Explorer). I hope the MS split will fix such political issues in the components. I hate politics and dirty manipulations. Aric.

I think you are going to have to build your own message handler for WM_LMOUSEDOWN and WM_LMOUSEUP on your ComboBox. You can refer to MSDN article Q170570 on how to do it. I was able move ComboBox on the form, but it is going to behave different depending on the Style property of your ComboBox. If your combo is a "Dropdown List" it will work just fine. If your combo is a "Dropdown Combo" you will be able to drag it only by the border or dropdown arrow. If you set your style to be a "Simple Combo" you will only be able to drag it by the border. In the case of "Simple Combo" and "DropDown Combo" when user clicks in the area of the combo box where he/she can type you do not recieve WM_LBUTTONDOWN message. That is probably why they did not expose MouseDown and MouseUp events in the first place. Well, this is all I can come up with right now. I hope this info will help you.

Thank you. Your response to my clipboard question was very helpful.

Your code could look something like that (providing you are using ADO): MyConnection.Open MyConnectionString MySQL = "INSERT INTO MyTable(MyField) VALUES('" & _ txtName.Text & "')" MyConnection.Execute MySQL MyConnection.Close I hope this helps.

sub beforeload() msgbox "Hello World" end sub

It's really cool - it's a full featured HTML browser that you can drop right into your apps! I think that there's an example project on CodeProject that demonstrates how to use it... if not, I'll write one up (we found some pretty cool things to do with it at work). To use it, you just drop it onto your form. Then in code you can use its Navigate() or Navigate2() functions to tell it to show some HTML page. It fires events when interesting things happen - like the user clicking on a hyperlink, or other things like that. Take a look at its properties and methods in the object browser - they're all pretty self explanatory. I'd advise creating a test project and just playing around with it for a day or two :)

I don't think that VB can use function pointers to call functions (although I'm not 100% positive). You can Declare a function and use it in VB (see docs on the Declare keyword). However your app will fail to load if wtsapi32.dll isn't on the system. A solution for this would be to encapsulate all your WTS calls in a COM object in a separate DLL. Then, if your app wants to make some WTS calls, it can create an instance of this COM object and do what needs to be done. When your app isn't on a terminal server, it won't ever create this COM object. Another solution would be to create a "stub" DLL, in C, that wrapped each function in wtsapi32 you wanted to call. Use the Declare keyword in your VB app to import each of these functions from your stub DLL. Then, when you wanted to call a certain wtsapi32 function, you'd instead call one of your stub dll's functions to do the dirty work (GetProcAddress(), call function, package return values and other info, then pass back to the calling VB function). If your project is mainly VB, I'd take solution #1. If your project is enough of a mix of C and VB that you don't mind maintaining the C stub as part of the project, go for #2.