Hi ,

I found a perfect solution on this website to solve the "server busy " error , by closing all running mappoint processes.

Dim proc As New Process
Dim procs As Process()
Dim i As Integer
procs = proc.GetProcessesByName("MapPoint")
If procs.Length = 0 Then Return 'MP wasn't loaded, so return
For i = 0 To UBound(procs)
procs(i).Kill()
procs(i).WaitForExit()
Next

This code is only working in VB.NET.

Can anyone please help to give alternative code in VB6?

Thanks a lot ,

wim

hi

Can anyone please help to give alternative code in VB6?

i am also looking for the same..

Regards,
Lalit Goyal

Hi,

Can anyone please help to give alternative code in VB6?

In traditional win32 code you can use the similar API calls FindWindow() to find the process window handle and to close it you can post a WM_QUIT message to it with PostMessage().

However killing the various active Mappoint instances will free up a lot of memory thus making all faster, and therefore less chance to get the 'server busy', so it is not _the_ solution to get rid of it.

This was an excellent idea.
I needed the same for my car navigation project, but it is written in C#, so I will post this for you:

Code:

Process[] procs;
procs = Process.GetProcessesByName("MapPoint") ;
if(procs.Length > 0)
{
	for&#40;int i=0;i<procs.Length;i++&#41;
	&#123;
		procs&#91;i&#93;.Kill&#40;&#41; ;
		procs&#91;i&#93;.WaitForExit&#40;&#41;;
	&#125;
&#125;

Hi,

or even more simple:

Code:

            Process[] processes = Process.GetProcessesByName("MapPoint");
            foreach (Process proc in processes)
                proc.Kill();

I also dont think you have to use WaitForExit because the process is killed as it will do same as task manger.
However be aware that if a user has started an instance of mappoint.exe this one is killed also !

I too have spent countless Dev hours using mappoint and love it. Recently when incorporating some longer queries, Started getting the 'Server Busy' stuff. Cannot seem to solve it as it is inconsistant. I don't want this message as the query always works and DB connection has it's own diagnostics anyway!! If their is a way to avoid this in VB6 I would be happy.

Any help very much appreciated

Hi,

The 'server busy' msg window comes when the calling (your) application does not respond to windows messages anymore. For example you will have this a lot if you step with the debugger trough the code.

Cleaning up mappoint.exe is helpfull whilst developping because a lot of time the program will not 'nice' terminating. In final fase it should not be done.

About the non responsive. If your program has many things to do in a closed loop then it should be into consideration to eather optimize it for speed, or run it in a background thread context. That way to not get the 'server busy' message.

I appreciate the reply. I do understand what is going on. A bit disappointed that this ActiveX control behaves differently than others when intercepting events. Don't get Server Busy when I step through code relating to MSChart for instance.

Anyway, I did solve the problem by offloading the queries into a second thread context although I am now a little worried about side effects.

Thanks
ITview

Hi,

Executing the lenghty code in a second thread is indeed the solution. You will have no side effects if the main application dont touch the data until the thread has finished his query.

a solution could be that the thread post a message to the main thread just before suspending (or destroying). the custom message handler in main thread can handle the data then.