Devart Forums

I'm not speaking from Devart behalf! Right now 64bit is pointless to even to consider for any Component Writer, until Codegear releases a Delphi 64bit compiler. Codegear was chatting about cleaning up the language to make it possible, until we know what the changes are we can’t even consider it until it’s release.

So their is no way to properly test for a SQL Connection, and the Unstable Network/ Disconnect mode just buggy ? I've followed the help, on these topics, but is way to unstable for a production enviroment. If I am wrong show me how this suppose to work!

I belive the GExpert Tools can do that for you.

http://www.gexperts.org/

I’m looking for the best way to Test a MSSQL Connection, before connecting to it. My current way of testing the connection , on a failed connection take one whole minute to trap. That’s way too long even with low timeouts.

I’ve read the documentation on Unstable Network / Disconnect Mode. How do you handle master/detail relationships what are the best practices in using these modes, I can’t find good examples.

Look forward to the responses!
Thanks

Kenny

I went to install the native client, and found a newer one is already installed.
All the machines that are having problems are XP Pro SP3. Is there an issue here with SP3?

SDAC 4.50 - SQL2005

I've been getting this message on 5% of my clients, and always the same clients.

"TCP Provider: An existing connection was forcibly closed by the remote host."

Everything works great for everyone else, I've checked for Server Configuration Issues, Network Issues, and I can't reason why I'm getting this problem. All the Clients are Hire-wired to 1000gb connection. I know this sounds like not a SDAC problem, but I was wondering if anyone had Connection Configuration tips that I can set to help make sure the connection is not forcibly Closed by MSSQL? Also I only started getting this problem after I upgraded from SQL2000 to SQL2005 and SDAC 3+ - SDAC 4.5.

I look forward to any suggestions!

Thanks Ken

I just purchased an upgrade from SDAC 3 to SDAC 4.35.0.14.
I'm using Win32 Delphi 2006 SP2 & SDAC 4.35.0.14. On SQL 2005.

I rebuilt by Application after the upgrade and launched my application.
All portions of my application crashed. Taking a closer look the Memo field
Is no longer support for ntext . You have to use a WideMemo. I rebuilt a
portion of my program under WideMemo Tfield. To Find out Infopower
and some other components can’t properly display the field, and gives me
The “Invalid input value”. I need Memo Support, I never had a problem
with Memo support until now.

Should SDAC start having SQL modes, SQL 7, SQL2000, SQL 2005, SQL 2008
This way you don’t break support models?

For now I’m reverting back to SDAC 3, so SDAC 4 is useless to me.

Ken

I want to have strict updates enabled, but I want to trap the error message and do something. Is this possible? If not can I make a request for event OnStrictupdateError!

Thanks

Ken