Problems connecting to ODB with OmnisSQL

Reg Paling reg.paling at
Tue Mar 1 01:59:57 UTC 2022

Hi all,

Michael Houlberg mentioned in another thread:
 > Also, we’re having problems getting the other computers, other than 
the ODB host, to connect with the OmnisSQL DAM. Has anyone else seen 
problems here?

I am starting another thread because I am hoping that this issue might 
see a bit of discussion in its own right...

Yes Michael, I am having difficult-to-diagnose problems.  In my case, 
these problems occur when the workstation is configured to skip the 
logon window and just automatically open the datafile with saved 
credentials.  If I turn the Logon window back on, then the small delay 
or interruption thus created seems to avoid the problem.

I have put some sleep() commands into the logic and they seem to (maybe) 
reduce the frequency of the issue but they don't totally remove it.

Sometimes I will get a "table not found" error from OmnisSQL, sometimes 
it hangs in other ways.

On affected computers it happens 10% or 20% of the time and the rest of 
the time it starts up without a problem.

I am not sure it is due to ODB v1.77 - I think it is more a Studio 10.2 

I have wrapped the logon in a repeat loop to try the connection again if 
it fails, but I can't always diagnose the failure.

Does anyone know exactly what this is?


More information about the omnisdev-en mailing list