My original post was totally unclear. Let me be more precise....

When our app tries to connect to the server (located on another machine) there is a possibility that the server is not online at that moment, or may be in the process of coming online. We want our app to 'look for the server' for a few seconds before giving up.

If the sever is available, there is a instant connection with db.connect.

However, if the server it NOT available, the db.connect method appears to have it's own timeout - approx 3 seconds. During that 3 seconds the db.connect seems to lock out the GUI.

This may be more a function of RB than the REALSQLServer/plug-in. We were looking for clarification on that.


We have everything in classes: i.e. we have a MainControllerClass, which has the main window (wMainClass) as a property... so in the open event of our application we instantiate an instance of the MainController class

Main = new MainControllerClass

Main.Init()

in the init method it prepares and opens the main window. Maybe it has something to do with that.

Another interesting thing came to light just now which may also have something to do with it.

If you create a new project, set it's main window to nothing and instantiate instances, it seems to behave a bit weird.

In the open event of the app you do the following:

  dim w as new wMainClass

  w.Visible = true

  MsgBox "Hello"


No matter what we do (w.visible, w.Refresh etc), the messagebox appears first.

Maybe not enough coffee yet.

Any thoughts?

- Jay

On Aug 14, 2006, at 1:31 PM, Roger Clary wrote:


On Aug 14, 2006, at 8:30 AM, Jay Wooten wrote:

It appears that when you issue a REALSQLServer connect call, it locks out the GUI for 2-3 seconds.

i.e. when our app is connecting to the server, we display a progress wheel to let the user know it is connecting.

However, when we issue  db.connect the GUI Freezes for 2-3 seconds.

So we tried putting the db.connect in a thread - same thing.. GUI locks up for 2-3 seconds.

We added a timer to the window to 'manually' refresh the progress wheel/window and that didn't help either.


Not seeing that behavior. Is the DB on the same machine as the app? If not, where is it?


Roger M. Clary
Class One Software
http://www.classonesoftware.com
[EMAIL PROTECTED]

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to