For a foolproof solution you would probably have to send a command to
the database. Something simple like "SELECT 1". If it errors, you're not
connected, if it's successful you are connected.
Try a combination of the two.
Brad
--
*********************************************************************************
www.PowerToTheBuilder.com
- Free, full featured database development tool for ASE and SQL Server
- Take control of your GUI with a free PB user control library
*********************************************************************************
Good luck,
Terry [TeamSybase] and Sequel the techno-kitten
--
*********************************
Build your vocabulary and feed the hungry
http://www.freerice.com
*********************************
Newsgroup User Manual
=====================
TeamSybase <> Sybase employee
Forums = Peer-to-peer
Forums <> Communication with Sybase
IsNull (AnswerTo (Posting)) can return TRUE
Forums.Moderated = TRUE, so behave or be deleted
*********************************
Sequel's Sandbox: http://www.techno-kitten.com
Home of PBL Peeper, a free PowerBuilder Developer's Toolkit.
Version 4.0.3 now available at the Sandbox
PB Futures updated Jan 2/2008
See the PB Troubleshooting & Migration Guides at the Sandbox
^ ^
o o
=*=
Because you have to attempt to connect the transaction object, then
you can check it's sqlcode.
In article <4787d5b2$1@forums-1-dub>, seq...@techno-kitten.com says...