With C++ it's easy - turn on the managed code option (/clr) in your project settings, and rebuild. --Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Ford, what's this fish doing in my ear?

Yes, i want to do it Run time when i will click on certain button.

A tooltip for an icon you add to the taskbar? If so, you can set the szTip member of the NOTIFYICONDATA struct you pass to Shell_NotifyIcon() to set the standard tooltip text. NIF_TIP needs to be added to the uFlags member as well. Mark "Great job, team. Head back to base for debriefing and cocktails." (Spottswoode "Team America")

My first post I suggested an alternative design solution for the OP, since I'm under the impression that he had selected the wrong solution for the problem. You don't paint the walls with a hammer. In my second post I was really trying to help you to avoid troubles in your way of doing multithreaded applications. spielehelfer wrote: - I thought its well known whats able to fill 'params' with - the Threadobject would be deleted after the loop jumps out, what happens when the thread has ended (I didnt write it, ok). Ok, so noted. A word of caution though: don't assume that the person you're trying to help is aware of things you consider 'common knowledge'. In my opinion it's hard enough to help someone while guessing their level of expertise. spielehelfer wrote: - that the Sleep() is no 100% secure statement for a threadchange ist true True, in fact it might be quite the opposite: it's almost 100% wrong to use ::Sleep() in this situation. ::Sleep(0) would make a little more sense but it would still not be quite right. Read the timing section [^] of Joe Newcomer's article and you will know why afterwards. spielehelfer wrote: - to secure the application for deadlocks, there are several locking mechanism possible so secure shared variables :suss: A "deadlock" and "corrupt data due to multiple threads accessing the same data" are two very different problems, but both are related to multithreading. Protecting shared data is often called "thread synchronization". You cannot prevent deadlocks by the use of thread synchronization; you may, however, cause a deadlock by improper use of thread synchronization. spielehelfer wrote: - WaitForSingleObject has the problem that it locks up the application that calls it if used tirect in a window creating code, thats why i used a loop If it's the blocking part you worry about I can tell you that your loop solution is worse. (Calling ::Sleep()!) :-> It really doesn't matter: you should use ::WaitForSingleObject(), or ::WaitForMultipleObjects(), for multiple reasons (the ones below at the top of my head): 1. you can set a timeout 2. t

All you have to do is add the appropriate switches to the command line that your using to launch Access, usually something like: C:\\Program Files\\Microsoft Office\\Office\\MSACCESS.EXE /repair You have to specify the full path to the .EXE. Dave Kreskowiak Microsoft MVP - Visual Basic

Hi I believe there is some property that you can set using the ADO Fields collection... not sure though. Have you tried googling for it? Chandra

Maybe then you will need to look at _how_ you are adding / deleting columns, since I have done this many times with Access 97 and it seems to work fine. Chandra

By large data do you mean "many records" or "large binary blobs"? The "many records" issue can often be helped by better indexing, and query reorganization.

Sunil, You just answered your own question. (Guy goes to the doctor and says "Doctor, it hurts when I do this." Doctor says, (all together now),) "DON'T DO THAT!" The problem is not on your database side, it is on the client side, in your code. Yes, using a for loop and adding one record at a time is the SLOWEST way to fill the grid. Use databinding if at all possible. But first of all, you haven't provided enough information to really help here. Can't fix what ya can't see. Tell which version of VB, which datagrid component you are using, which type of backing store you are filling the grid from (ADO recordset, .Net datatable, datareader, whatever), and show the sql. :)